Re: [v8-users] Segmentation fault when creating new v8 context.
Its not about our complicated code, its about simple Hello World example from official site. And all detailed reproduction steps are the official Getting Started instruction with one detail - it was used for Ubuntu 12.04 x64 and i wrote about it. :) *In any case my problem was solved in revision 13714 of v8. * But its really strangely, that standard example not worked in a public revision. :) Thanks for your attention. :) четверг, 21 февраля 2013 г., 18:44:40 UTC+4 пользователь Sven Panne написал: I don't even know what to compile from https://code.google.com/p/v8-juice/source/browse/, the trunk seems to be out of date, it uses e.g. GetPointerFromInternalField and friends which are not part of v8's external API anymore. So until I see some stand-alone repro, I'll ignore this issue from now on. Note that we are really willing to help embedders, but digging through someone else's code with only vague hints is a huge waste of time. If our build bots are OK, Chrome works fine running through hundreds of thousands of web pages and tests etc. it is really not the obligation of the v8 team to prove that there are no bugs. If you encounter a problem, open a bug on our bug tracker, including reliable, detailed reproduction steps, and we'll take a look. Another hint: The external v8 API is undergoing some changes, mainly making the use of an Isolate explicit and mandatory. To be prepared, I strongly recommend embedders to remove the V8_DISABLE_DEPRECATIONS line from include/v8.h for testing purposes. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups v8-users group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
On Mon, Feb 25, 2013 at 1:43 PM, Егор Яковлев goga@gmail.com wrote: But its really strangely, that standard example not worked in a public revision. :) All V8 revisions are public. Sometimes they're broken, and sometime they're newer than the documentation. It happens with projects that are under active development. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups v8-users group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
Sorry, I just do not know the specifics :) понедельник, 25 февраля 2013 г., 17:39:44 UTC+4 пользователь Jakob Kummerow написал: On Mon, Feb 25, 2013 at 1:43 PM, Егор Яковлев goga...@gmail.comjavascript: wrote: But its really strangely, that standard example not worked in a public revision. :) All V8 revisions are public. Sometimes they're broken, and sometime they're newer than the documentation. It happens with projects that are under active development. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups v8-users group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
On Thu, Feb 21, 2013 at 3:44 PM, Sven Panne svenpa...@chromium.org wrote: I don't even know what to compile from https://code.google.com/p/v8-juice/source/browse/, the trunk seems to be out of date, it uses e.g. GetPointerFromInternalField and friends which are not part of v8's external API anymore. The main project tree there is historical and no longer maintained. Only the /convert directory (the one i sent the links to) is current vis-a-vis v8's API (or was, until 2 days ago), and we removed GetPointerFromInternalField() from it over the holidays because its deprecation/behaviour change broke our class-binding mechanism. Note that we are really willing to help embedders, but digging through someone else's code with only vague hints is a huge waste of time. As is digging through v8 to find what v8 changes broke our (unchanged) code. So nobody wins. While trying to create a reproducible test case for you, i found 2 things: a) the Hello World example in the v8 docs no longer compile due to API changes. https://developers.google.com/v8/get_started b) the assertion problem has magically disappeared in the meantime (using r13713). Another hint: The external v8 API is undergoing some changes, mainly making the use of an Isolate explicit and mandatory Where can we find documentation on how to do this? i'm currently looking over the v8 docs (https://developers.google.com/v8/) and i see neither hide nor hair of Isolates. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups v8-users group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
On Wed, Feb 20, 2013 at 4:34 PM, Егор Яковлев goga@gmail.com wrote: I have the same problem. I built v8 for x64 architecture on Ubuntu 12.04 using gyp. And now i try to run the Hello World example. But i have Segmentation fault (core dumped). This error occurs when creating new v8 context. Same here, using: [stephan@host:~/src/google/v8]$ svn info Path: . URL: http://v8.googlecode.com/svn/trunk Repository Root: http://v8.googlecode.com/svn Repository UUID: ce2b1a6d-e550-0410-aec6-3dcde31c8c00 Revision: 13700 Node Kind: directory Schedule: normal Last Changed Author: yang...@chromium.org Last Changed Rev: 13692 Last Changed Date: 2013-02-19 14:55:47 +0100 (Tue, 19 Feb 2013) Ubuntu 12.04 on x64, gcc 4.6.3. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups v8-users group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
On Thu, Feb 21, 2013 at 9:54 AM, Stephan Beal sgb...@googlemail.com wrote: On Wed, Feb 20, 2013 at 4:34 PM, Егор Яковлев goga@gmail.com wrote: I have the same problem. I built v8 for x64 architecture on Ubuntu 12.04 using gyp. And now i try to run the Hello World example. But i have Segmentation fault (core dumped). This error occurs when creating new v8 context. Same here, using: [stephan@host:~/src/google/v8]$ svn info Path: . URL: http://v8.googlecode.com/svn/trunk Repository Root: http://v8.googlecode.com/svn Repository UUID: ce2b1a6d-e550-0410-aec6-3dcde31c8c00 And on the bleeding edge: [stephan@host:~/src/google/v8]$ svn info Path: . URL: http://v8.googlecode.com/svn/branches/bleeding_edge Repository Root: http://v8.googlecode.com/svn Repository UUID: ce2b1a6d-e550-0410-aec6-3dcde31c8c00 Revision: 13700 Node Kind: directory Schedule: normal Last Changed Author: yang...@chromium.org Last Changed Rev: 13700 Last Changed Date: 2013-02-20 15:29:40 +0100 (Wed, 20 Feb 2013) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups v8-users group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
On Thu, Feb 21, 2013 at 9:54 AM, Stephan Beal sgb...@googlemail.com wrote:
Same here, using:
[stephan@host:~/src/google/v8]$ svn info
Path: .
URL: http://v8.googlecode.com/svn/trunk
Repository Root: http://v8.googlecode.com/svn
Repository UUID: ce2b1a6d-e550-0410-aec6-3dcde31c8c00
Revision: 13700
i've been able to narrow this down to being introduced somewhere between:
-r{20130215T00Z} (OK)
and
-r{20130220T00Z} (Not OK)
but my boss (who wants me doing something completely different) is losing
patience with me, so i won't be able to investigate it further.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
v8-users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
On Thu, Feb 21, 2013 at 11:39 AM, Stephan Beal sgb...@googlemail.comwrote:
i've been able to narrow this down to being introduced somewhere between:
-r{20130215T00Z} (OK)
and
-r{20130220T00Z} (Not OK)
One more...
-r{20130218T00Z}
does not exhibit this problem.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
v8-users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
Sorry, what do you mean by:
-r{20130218T00Z}
Is the revision number for v8 or something else? :)
четверг, 21 февраля 2013 г., 14:48:05 UTC+4 пользователь Stephan Beal
написал:
On Thu, Feb 21, 2013 at 11:39 AM, Stephan Beal
sgb...@googlemail.comjavascript:
wrote:
i've been able to narrow this down to being introduced somewhere between:
-r{20130215T00Z} (OK)
and
-r{20130220T00Z} (Not OK)
One more...
-r{20130218T00Z}
does not exhibit this problem.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
v8-users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
On Thu, Feb 21, 2013 at 10:22 PM, Егор Яковлев goga@gmail.com wrote:
Sorry, what do you mean by:
-r{20130218T00Z}
Is the revision number for v8 or something else? :)
It looks like a timestamp to me. So the problem was introduced some
time between Feb 18th and Feb 20th, a two-day possible period.
ChrisA
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
v8-users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
What are the detailed steps to reproduce this? -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups v8-users group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
On Thu, Feb 21, 2013 at 12:42 PM, Sven Panne svenpa...@chromium.org wrote:
What are the detailed steps to reproduce this?
- Update to the latest version
- rebuild any custom v8 client app of your choice which has worked for the
past year or more.
- start that app
- crash at startup:
#
# Fatal error in ../src/v8threads.cc, line 53
# CHECK(isolate != __null) failed
#
C stack trace ===
1: V8_Fatal
2: v8::Locker::Initialize(v8::Isolate*)
3: v8::Locker::Locker(v8::Isolate*)
4: ??
5: ??
6: ??
7: ??
8: __libc_start_main
9: ??
All of my v8 apps crash at startup with the current trunk v8. The last
working versions i was able to test was -r{20130218T00Z}, which
resolves to -r13679.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
v8-users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
OK, my apps are d8 and Chrome, and both work. :-) Seriously, we need more detailed steps and not just some fuzzy prose. It could very well be the case that some applications embedding v8 worked only by accident, so a stand-alone reproduction is really needed, e.g. a single small C/C++ file embedding v8 which crashes for you when compiled and run. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups v8-users group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
On Thu, Feb 21, 2013 at 2:03 PM, Sven Panne svenpa...@chromium.org wrote:
OK, my apps are d8 and Chrome, and both work. :-) Seriously, we need more
detailed steps and not just some fuzzy prose. It could
i understand that, but you cannot expect us to go decompose our apps every
time new v8 behaviour breaks something as basic as application startup
(this isn't the first time in the past 6 months my apps start mysteriously
breaking due to mysterious v8 changes). Here's what i know, without going
so far as to write a new app which demonstrates this problem (i have
several which demonstrate it already)...
-r{20130218T00Z} works for me
-r{20130220T00Z} does not work for me
very well be the case that some applications embedding v8 worked only by
accident, so a stand-alone reproduction is really needed, e.g. a single
small C/C++ file embedding v8 which crashes for you when compiled and run.
The apps i have which break with the newer versions have worked for 18+
months without any modifications on my side. If they only worked by
accident then something is horribly wrong with v8 (because my apps are all
modeled after the shell example app and the sparse documentation from the
v8 team). None of my apps are extremely trivial, so i have no trivial
example. All of them use the same startup process, however, and that is
where v8 is failing for several of us. Here's an example which crashes:
https://code.google.com/p/v8-juice/source/browse/convert/addons/shell-skel/shell.cpp#65
during initialization, which happens here:
https://code.google.com/p/v8-juice/source/browse/convert/include/cvv8/V8Shell.hpp#175
the part which craps out is the v8::Locker constructor, which is literally
the first value initialized in my app after main() is entered, before any
of my app-specific code gets run. The crash dump and backtrace look like:
[stephan@host:~/cvs/v8-juice/convert/addons/shell-skel]$ gdb --args ./shell
test.js
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://bugs.launchpad.net/gdb-linaro/...
Reading symbols from
/home/stephan/cvs/v8-juice/convert/addons/shell-skel/shell...done.
(gdb) r
Starting program:
/home/stephan/cvs/v8-juice/convert/addons/shell-skel/shell test.js
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
#
# Fatal error in ../src/v8threads.cc, line 53
# CHECK(isolate != __null) failed
#
C stack trace ===
1: V8_Fatal
2: v8::Locker::Initialize(v8::Isolate*)
3: v8::Locker::Locker(v8::Isolate*)
4: ??
5: ??
6: ??
7: ??
8: __libc_start_main
9: ??
JS stack trace is not available ===
Isolate for the thread is not initialized =
Program received signal SIGTRAP, Trace/breakpoint trap.
v8::internal::OS::DebugBreak () at ../src/platform-linux.cc:427
warning: Source file is more recent than executable.
427 #elif defined(__mips__)
(gdb) bt
#0 v8::internal::OS::DebugBreak () at ../src/platform-linux.cc:427
#1 0x776fcfff in v8::internal::OS::Abort () at
../src/platform-linux.cc:409
#2 0x7732281e in V8_Fatal (file=0x7779e749
../src/v8threads.cc, line=53, format=0x7779e45e CHECK(%s) failed)
at ../src/checks.cc:59
#3 0x7761f569 in v8::Locker::Initialize (this=0x7fffe160,
isolate=0x0) at ../src/v8threads.cc:53
#4 0x7734e5ff in v8::Locker::Locker (this=0x7fffe160,
isolate=0x0) at ../src/../include/v8.h:4003
#5 0x00404c99 in cvv8::Detail::V8MaybeLockertrue::V8MaybeLocker
(this=0x7fffe160) at ../../include/cvv8/V8Shell.hpp:33
#6 0x00404555 in cvv8::V8Shelltrue::V8Shell
(this=0x7fffe160, globalObjectName=0x0, argc=2, argv=0x7fffe338,
argOffset=1) at ../../include/cvv8/V8Shell.hpp:181
#7 0x00403c7c in v8_main (argc=2, argv=0x7fffe338) at
shell.cpp:65
#8 0x00403f7b in main (argc=2, argv=0x7fffe338) at
shell.cpp:136
The problem is obviously the NULL Isolate. My v8 client code has _never_
(in the 4-some-odd years i've been using v8) explicitly used an Isolate, so
i find the it worked by accident hypothesis hard to swallow.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
v8-users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-users+unsubscr...@googlegroups.com.
For more options, visit
Re: [v8-users] Segmentation fault when creating new v8 context.
I don't even know what to compile from https://code.google.com/p/v8-juice/source/browse/, the trunk seems to be out of date, it uses e.g. GetPointerFromInternalField and friends which are not part of v8's external API anymore. So until I see some stand-alone repro, I'll ignore this issue from now on. Note that we are really willing to help embedders, but digging through someone else's code with only vague hints is a huge waste of time. If our build bots are OK, Chrome works fine running through hundreds of thousands of web pages and tests etc. it is really not the obligation of the v8 team to prove that there are no bugs. If you encounter a problem, open a bug on our bug tracker, including reliable, detailed reproduction steps, and we'll take a look. Another hint: The external v8 API is undergoing some changes, mainly making the use of an Isolate explicit and mandatory. To be prepared, I strongly recommend embedders to remove the V8_DISABLE_DEPRECATIONS line from include/v8.h for testing purposes. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups v8-users group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [v8-users] Segmentation fault when creating new v8 context.
I just built SilkJS from a fresh git clone and it runs. No segfault. This was on OSX Mountain Lion. Part of the build process is to checkout the latest v8 from svn. On Thursday, February 21, 2013 6:44:40 AM UTC-8, Sven Panne wrote: I don't even know what to compile from https://code.google.com/p/v8-juice/source/browse/, the trunk seems to be out of date, it uses e.g. GetPointerFromInternalField and friends which are not part of v8's external API anymore. So until I see some stand-alone repro, I'll ignore this issue from now on. Note that we are really willing to help embedders, but digging through someone else's code with only vague hints is a huge waste of time. If our build bots are OK, Chrome works fine running through hundreds of thousands of web pages and tests etc. it is really not the obligation of the v8 team to prove that there are no bugs. If you encounter a problem, open a bug on our bug tracker, including reliable, detailed reproduction steps, and we'll take a look. Another hint: The external v8 API is undergoing some changes, mainly making the use of an Isolate explicit and mandatory. To be prepared, I strongly recommend embedders to remove the V8_DISABLE_DEPRECATIONS line from include/v8.h for testing purposes. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups v8-users group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[v8-users] Segmentation fault when creating new v8 context.
Hi All, I am getting segmentation fault while using v8 library when creating new v8 context, Program received signal SIGSEGV, Segmentation fault. 0x2b9434f8 in v8::internal::SharedFunctionInfo::code () Please provide me an input if you have any. Thanks Regards, Nilima -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users
Re: [v8-users] Segmentation fault when creating new v8 context.
Hi Nilima - Was this on v8mips, or on v8 for one of the other architectures? If for v8mips, are you running big-endian or little-endian? thanks, paul On Aug 10, 2010, at 3:11 AM, Nilima Chavan wrote: Hi All, I am getting segmentation fault while using v8 library when creating new v8 context, Program received signal SIGSEGV, Segmentation fault. 0x2b9434f8 in v8::internal::SharedFunctionInfo::code () Please provide me an input if you have any. Thanks Regards, Nilima -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users
