A quick update:

I managed to get bigger call stack on Android 4.4.2 device (the previous 
one was Android 5.1.1). Here is the stack

Thread [1] 29168 [core: 0] (Suspended : Signal : SIGILL:Illegal instruction) 
v8::base::OS::Abort() at platform-posix.cc:228 0x617ac930 
V8_Fatal() at logging.cc:116 0x617a820c 
v8::internal::SafeStackFrameIterator::Advance() at frames.cc:346 0x610af4d8 
v8::internal::SafeStackFrameIterator::SafeStackFrameIterator() at 
frames.cc:242 0x610aed30 
v8::internal::TickSample::Init() at sampler.cc:613 0x613f9424 
v8::internal::Sampler::SampleStack() at sampler.cc:717 0x613f9a64 
v8::internal::SignalHandler::HandleProfilerSignal() at sampler.cc:488 
0x613f8c08 
0x400218a8 


On Tuesday, December 1, 2015 at 10:32:06 AM UTC+2, Jochen Eisinger wrote:
>
> Hi!
>
> can you provide some stack traces, or at least some info on where it 
> actually crashes?
>
> best
> -jochen
>
> On Mon, Nov 30, 2015 at 6:16 PM Mihail Slavchev <mihail....@gmail.com 
> <javascript:>> wrote:
>
>> Hi guys,
>>
>> NativeScript developer here. We embed V8 (4.5.103) in android apps and I 
>> am trying to diagnose an app crash (SIGILL) when the CPU profiler is 
>> enabled. It happens on ARM architecture, both on devices and emulators, and 
>> as far as I observed it happens only in stacks with mixed JavaScript, C++ 
>> and Java frames. Most often the crash happens 
>> in v8::internal::SignalHandler::HandleProfilerSignal but I saw it also to 
>> happen a few times in stack unwinding methods. I am not able to reproduce 
>> the crash on x86, both on devices and emulators.
>>
>> I realize it is quite a corner case and I am looking for ways to collect 
>> more information so I can diagnose the crash better. Using debug build 
>> doesn't give me more information. Are there any build flags or other means 
>> so I can collect more data? Any ideas are appreciated.
>>
>> TIA,
>> Mihail
>>
>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@googlegroups.com <javascript:>
>> 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+u...@googlegroups.com <javascript:>.
>> 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.

Reply via email to