Comment #3 on issue 3301 by svenpa...@chromium.org: repeatedly allocation
causes segfault
http://code.google.com/p/v8/issues/detail?id=3301
Hmmm, I still can't reproduce this, I tried memcheck with both ia32 and x64
versions of d8. It would be great if you can build a debug version ("make
x64.debug" or "make ia32.debug", don't know what platform you're compiling
for) and get a backtrace via gdb.
Furthermore, the git hashes are a bit hard to work with, the master is
still in SVN (http://v8.googlecode.com/svn/branches/bleeding_edge/) and the
hashes are different for every repository because of this. SVN revision
numbers are more helpful.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
