Hi Soren, thanks for your prompt response and useful links to those issues! I have starred them :)
Sincerely, Ondrej 2010/10/1 Søren Gjesse <[email protected]> > Hi, > > a) This is not the expected behavior, opened issue > 888<http://code.google.com/p/v8/issues/detail?id=888> > . > b) This is "by design" as the ia32 version of V8 is still the most widely > used. Most developers have 64-bit OSes, but most likely want to build the > ia32 version. Issue 429 <http://code.google.com/p/v8/issues/detail?id=429>is > open on this > > Regards, > Søren > > On Fri, Oct 1, 2010 at 08:53, ondras <[email protected]> wrote: > >> Hi, >> >> I have two questions regarding my recent experiments with latest V8 >> revisions. >> >> a) In my embedding (v8cgi), I would like to start the debugger agent >> and (optionally) wait for the connection. In order to do this, I added >> a third argument to v8::Debug::EnableAgent (http://code.google.com/p/ >> v8cgi/source/browse/trunk/src/v8cgi.cc#183<http://code.google.com/p/v8cgi/source/browse/trunk/src/v8cgi.cc#183>). >> However, the V8 normally >> starts executing code, even if wait_for_debugger == true. What am I >> doing wrong? >> >> b) Compiling V8 on x64 is still kind of painful, as the architecture >> autodetection does not work right - by default, V8 tries to compile in >> 32bit mode (so I must always add "arch=x64"). Is there any hope this >> might get improved? >> >> >> Thanks, >> Ondrej Zara >> >> -- >> v8-users mailing list >> [email protected] >> http://groups.google.com/group/v8-users >> > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
