Re: [v8-users] d8 binary seg faults when moved?

2015-09-04 Thread Jakob Kummerow
GYP_DEFINES="v8_use_external_startup_data=0" should do the trick, but I
haven't tried it.

On Fri, Sep 4, 2015 at 8:37 PM, Charlie Andrews  wrote:

> ldd /tmp/d8 gives:
>
> linux-vdso.so.1 =>  (0x7ffd7bc52000)
>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7efedc7a5000)
>> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7efedc59d000)
>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>> (0x7efedc299000)
>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7efedbf93000)
>> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7efedbd7d000)
>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>> (0x7efedbb5f000)
>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7efedb79a000)
>> /lib64/ld-linux-x86-64.so.2 (0x7efedc9a9000)
>
>
> Moving natives_blob.bin and snapshot_blob.bin along with d8 does fix the
> problem! Is there any way to avoid having to do this and to package it up
> as one file instead? We use d8 as a dependency in our project, and ideally
> we'd like to only have to keep around one file rather than three. (This was
> how things worked as of 4.3.61, and is also how things seem to work on Mac.)
>
>
>
> On Friday, September 4, 2015 at 4:14:35 AM UTC-4, Jakob Kummerow wrote:
>>
>> You need to copy natives_blob.bin and snapshot_bob.bin along with d8.
>>
>> (There should probably be a better error message to indicate this.)
>>
>> On Thu, Sep 3, 2015 at 8:19 PM, Marcin Cieslak  wrote:
>>
>>> On Thu, 3 Sep 2015, 'Charlie Andrews' via v8-users wrote:
>>>
>>> > $ mv out/Release/d8 /tmp/d8
>>> > > $ /tmp/d8
>>> > > Segmentation fault (core dumped)
>>> >
>>> >
>>> > Does anyone know why this happens? Is there a way to build v8 so that
>>> I can
>>> > move it around and still have it start properly?
>>>
>>> What does your "ldd /tmp/d8" say? Also any backtrace?
>>>
>>> ~Marcin
>>>
>>
>> --
> --
> 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/d/optout.
>

-- 
-- 
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/d/optout.


Re: [v8-users] d8 binary seg faults when moved?

2015-09-04 Thread 'Charlie Andrews' via v8-users
That did the trick. Thank you both!

On Fri, Sep 4, 2015 at 2:42 PM, Jakob Kummerow 
wrote:

> GYP_DEFINES="v8_use_external_startup_data=0" should do the trick, but I
> haven't tried it.
>
> On Fri, Sep 4, 2015 at 8:37 PM, Charlie Andrews 
> wrote:
>
>> ldd /tmp/d8 gives:
>>
>> linux-vdso.so.1 =>  (0x7ffd7bc52000)
>>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7efedc7a5000)
>>> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7efedc59d000)
>>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>>> (0x7efedc299000)
>>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7efedbf93000)
>>> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7efedbd7d000)
>>> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
>>> (0x7efedbb5f000)
>>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7efedb79a000)
>>> /lib64/ld-linux-x86-64.so.2 (0x7efedc9a9000)
>>
>>
>> Moving natives_blob.bin and snapshot_blob.bin along with d8 does fix the
>> problem! Is there any way to avoid having to do this and to package it up
>> as one file instead? We use d8 as a dependency in our project, and ideally
>> we'd like to only have to keep around one file rather than three. (This was
>> how things worked as of 4.3.61, and is also how things seem to work on Mac.)
>>
>>
>>
>> On Friday, September 4, 2015 at 4:14:35 AM UTC-4, Jakob Kummerow wrote:
>>>
>>> You need to copy natives_blob.bin and snapshot_bob.bin along with d8.
>>>
>>> (There should probably be a better error message to indicate this.)
>>>
>>> On Thu, Sep 3, 2015 at 8:19 PM, Marcin Cieslak  wrote:
>>>
 On Thu, 3 Sep 2015, 'Charlie Andrews' via v8-users wrote:

 > $ mv out/Release/d8 /tmp/d8
 > > $ /tmp/d8
 > > Segmentation fault (core dumped)
 >
 >
 > Does anyone know why this happens? Is there a way to build v8 so that
 I can
 > move it around and still have it start properly?

 What does your "ldd /tmp/d8" say? Also any backtrace?

 ~Marcin

>>>
>>> --
>> --
>> 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/d/optout.
>>
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/v8-users/3fQiwMi6_jc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Charlie Andrews | Software Engineer | charl...@google.com

-- 
-- 
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/d/optout.


[v8-users] Separate build directories created for V8

2015-09-04 Thread Manmohan Bishnoi
I checked out latest V8 source into this directory */mydisk/V8*

fetch v8
cd v8
gclient sync
make x64.release -j8 OUTDIR=/mydisk/codebase/js_v8_x64 library=shared 
debuggersupport=off i18nsupport=off

The above commands completed successfully and created two directories:

   1. */mydisk/codebase/js_v8_x64* : This directory has various Makefiles
   2. */mydisk/V8/v8/mydisk/codebase/js_v8_x64* : This directory has a "
   *x64.release*" named sub-directory with all the binaries inside.

Is this normal behavior?
I was expecting "*x64.release*" directory to be inside 
*/mydisk/codebase/js_v8_x64*


However if I build using:


make x64.release -j8 *OUTDIR=js_v8_x64_2* library=shared 
debuggersupport=off i18nsupport=off


Then a directory is created at */mydisk/V8/v8/js_v8_x64_2* with all the 
makefile and binaries inside it.

-- 
-- 
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/d/optout.


Re: [v8-users] d8 binary seg faults when moved?

2015-09-04 Thread Jakob Kummerow
You need to copy natives_blob.bin and snapshot_bob.bin along with d8.

(There should probably be a better error message to indicate this.)

On Thu, Sep 3, 2015 at 8:19 PM, Marcin Cieslak  wrote:

> On Thu, 3 Sep 2015, 'Charlie Andrews' via v8-users wrote:
>
> > $ mv out/Release/d8 /tmp/d8
> > > $ /tmp/d8
> > > Segmentation fault (core dumped)
> >
> >
> > Does anyone know why this happens? Is there a way to build v8 so that I
> can
> > move it around and still have it start properly?
>
> What does your "ldd /tmp/d8" say? Also any backtrace?
>
> ~Marcin
>

-- 
-- 
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/d/optout.