I am seeing a SIGILL crash too with my embedding app during profiling.
Here's the stack:
Thread [134] (Suspended: Signal 'SIGILL' received. Description: Illegal
instruction.)
40 v8::base::OS::Abort()
/space/projects/v8-git/v8/src/base/platform/platform-posix.cc:229
0x00007ffff64bcd11
39 V8_Fatal() /space/projects/v8-git/v8/src/base/logging.cc:116
0x00007ffff64b7901
38 v8::internal::SafeStackFrameIterator::Advance()
/space/projects/v8-git/v8/src/frames.cc:343 0x00007ffff5f29c39
37 v8::internal::SafeStackFrameIterator::SafeStackFrameIterator()
/space/projects/v8-git/v8/src/frames.cc:239 0x00007ffff5f29705
36 v8::internal::TickSample::Init()
/space/projects/v8-git/v8/src/sampler.cc:691 0x00007ffff631138b
35 v8::internal::Sampler::SampleStack()
/space/projects/v8-git/v8/src/sampler.cc:796 0x00007ffff631114f
34 v8::internal::SignalHandler::HandleProfilerSignal()
/space/projects/v8-git/v8/src/sampler.cc:562 0x00007ffff631109b
33 <signal handler called>() 0x000000311ca0f6d0
32 svc::Handle<xdmp::StaticEnv>::Handle()
/space/projects/v8upgrade/src/services/Handle.h:143 0x00000000025a3ef4
31 xdmp::ItemType::ItemType()
/space/projects/v8upgrade/src/XQuery.cpp:20447 0x000000000265bb99
30 xdmp::ItemDatatype::ItemDatatype()
/space/projects/v8upgrade/src/XQuery.cpp:20686 0x000000000265c43b
29 xdmp::constructType()
/space/projects/v8upgrade/src/JSEngine.cpp:2824 0x00000000034771ad
28 v8::internal::FunctionCallbackArguments::Call()
/space/projects/v8-git/v8/src/arguments.cc:33 0x00007ffff5bd3b6c
27 v8::internal::HandleApiCallHelper<true>()
/space/projects/v8-git/v8/src/builtins.cc:1576 0x00007ffff5c349fa
26 v8::internal::Builtin_Impl_HandleApiCallConstruct()
/space/projects/v8-git/v8/src/builtins.cc:1609 0x00007ffff5c343a9
25 v8::internal::Builtin_HandleApiCallConstruct()
/space/projects/v8-git/v8/src/builtins.cc:1605 0x00007ffff5c21820
24 <symbol is not available> 0x0000380e93a08b3b
23 <symbol is not available> 0x00007ffff05fed00
22 <symbol is not available> 0x0000380e93a08a81
21 <symbol is not available> 0x00007ffff05fece0
20 <symbol is not available> 0x00007ffff05fed58
19 <symbol is not available> 0x0000380e93a33ca4
18 <symbol is not available> 0x00002c9f540abaf1
17 <symbol is not available> 0x0000133cbc037991
16 <symbol is not available> 0x0000133cbc0379b9
15 <symbol is not available> 0x0000133cbc0379b9
14 <symbol is not available> 0x00002c9f540abaf1
13 <symbol is not available> 0x0000000100000000
12 <symbol is not available> 0x00002955b9704189
11 <symbol is not available> 0x0000380e93a33b21
10 <symbol is not available> 0x0000000900000000
9 <symbol is not available> 0x00002c9f540d7361
8 <symbol is not available> 0x00007ffff05fed98
7 <symbol is not available> 0x0000380e93a33ecc
6 <symbol is not available> 0x0000133cbc037991
5 <symbol is not available> 0x0000133cbc01ea49
4 <symbol is not available> 0x00002c9f540abaf1
3 <symbol is not available> 0x0000380e93a33de1
2 <symbol is not available> 0x0000000800000000
1 <symbol is not available> 0x0000000000000000
Same code runs fine without profiling. v8 version is 4.7.0. Now trying
against 3.24.
On Wednesday, December 9, 2015 at 9:18:43 PM UTC-8, Jim Acquavella wrote:
>
> Also, I can provide a binary with instructions on how to reproduce the
> problem. I'm using v8 version 4.5.35.
>
> On Wednesday, December 9, 2015 at 4:12:08 PM UTC-8, Jim Acquavella wrote:
>>
>> I'm seeing this same problem when I start cpu profiling. In my
>> case, StackFrameIteratorBase::SingletonFor is calling executing this line
>> with a type of 0x21000000.
>>
>> StackFrame* result = SingletonFor(type);
>>
>> SingletonFor returns NULL and DCHECK fails.
>>
>> On Tuesday, December 1, 2015 at 8:30:01 AM UTC-8, Mihail Slavchev wrote:
>>>
>>> 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>
>>>> 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
>>>>> 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.
>>>>> 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.
