Hi Jochen,
Thank you for the quick response. When I run the app under GDB (V8 is built
in debug) I get the following stack:
Thread [1] 14835 [core: 1] (Suspended : Signal : SIGSEGV:Segmentation fault)
0x0
v8::internal::SamplingCircularQueue<v8::internal::TickSampleEventRecord,
992u>::FinishEnqueue() at circular-queue-inl.h:55 0xa405ac14
I think the GDB gets confused and doesn't show all frames. Nevertheless,
here is the offending code fragment:
template<typename T, unsigned L>
void SamplingCircularQueue<T, L>::FinishEnqueue() {
base::Release_Store(&enqueue_pos_->marker, kFull);
enqueue_pos_ = Next(enqueue_pos_); // <== this is line 55 in
circular-queue-inl.h
}
template<typename T, unsigned L>
typename SamplingCircularQueue<T, L>::Entry* SamplingCircularQueue<T,
L>::Next(
Entry* entry) {
Entry* next = entry + 1;
if (next == &buffer_[L]) return buffer_;
return next;
}
I tried to examine "this" in the context and I get the following error
message:
buffer_
v8::internal::SamplingCircularQueue<v8::internal::TickSampleEventRecord,
992u>::Entry [992] Error: Multiple errors reported.\ Failed to execute MI
command: -var-create - * &(((this)->buffer_)) Error message from debugger
back end: Cannot access memory at address 0x13\ Failed to execute MI
command: -data-evaluate-expression ((this)->buffer_) Error message from
debugger back end: Cannot access memory at address 0x13\ Failed to execute
MI command: -var-create - * &(((this)->buffer_)) Error message from
debugger back end: Cannot access memory at address 0x13\ Unable to create
variable object
Seems like the stack is corrupted. I will give another try tomorrow. Also,
if needed I can provide a small repro.
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.
