Comment #2 on issue 3301 by [email protected]: repeatedly allocation
causes segfault
http://code.google.com/p/v8/issues/detail?id=3301
Thanks for looking into this.
Attaching more information:
- commit bbbb98aba5f2dd921bdf55ae415253f2c064f0ec doesn't segfault
- commit dc33fd73208fe05e811273b6c93505a554bcebe0 does
- I managed to repro this bug on two physically different machines (32bit
amd, and 64bit intel)
- I never managed to repro this on Debian Wheezy, only Squeeze
- On same host machine under two different virtualized guests I managed to
get segfault in one environment and not in other
- Two different libc versions that gave me segfault are attached
- On same machine ia32.release segfaults, ia32.debug doesn't
- valgrind output is attached
- d8 segfaults when interactive with "Array(30000);". d8.session.txt shows
this under valgrind
Does v8 support older glibc versions?
Attachments:
libc_version.txt 629 bytes
libc_version_second.txt 657 bytes
valgrind.output 4.1 KB
d8.session.txt 10.3 KB
--
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
[email protected]
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
