Thanks for the update. I've applied the patch against node 0.8.14's
For my simplest test case, the patch definitely helps. However for the
+ Handle<Object> error = GetProperty(global(), "Error");
So it seems like there are still situations where no stack trace will
On Wed, Nov 7, 2012 at 4:05 AM, Yang Guo <yang...@chromium.org> wrote:
> Hi Dave,
> I completed a patch fixing this problem. It's currently under review:
> You are welcome to point out any short-comings in this patch.
> The problem with your approach is that it reimplements the stack trace
> On Mon, Nov 5, 2012 at 1:27 PM, Dave Smith <d...@singly.com> wrote:
>> Hi Yang,
>> Thanks for the feedback. If you have the time/inclination to describe
>> On Mon, Nov 5, 2012 at 4:37 AM, Yang Guo <yang...@chromium.org> wrote:
>> > Hi Dave,
>> > I wasn't aware of this problem before. We currently already have
>> > Your current approach has some subtle problems. If you have some
>> > Yang
>> > On Mon, Nov 5, 2012 at 12:36 PM, Yang Guo <yang...@chromium.org> wrote:
>> >> Hi Dave,
>> >> I wasn't aware of this problem before. We currently already have
>> >> On Sat, Nov 3, 2012 at 4:02 AM, Dave Smith <diz...@singly.com> wrote:
>> >>> Hi,
>> >>> I've been using node.js (and hence, v8) for a little bit and one thing
>> >>> (note that it's against the fork of the node codebase, which embeds v8
>> >>> My lack of familiarity with v8 is probably grossly evident, but
>> >>> Thanks!
>> >>> D.
>> >>> --
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.