Bug 53288 - Crash in mini-exceptions during stress tests
Summary: Crash in mini-exceptions during stress tests
Status: NEW
Alias: None
Product: Runtime
Classification: Mono
Component: General (show other bugs)
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Alexander Kyte
URL:
Depends on:
Blocks:
 
Reported: 2017-03-13 18:55 UTC by Andi McClure
Modified: 2017-03-13 19:06 UTC (History)
2 users (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments

Description Andi McClure 2017-03-13 18:55:30 UTC
Connor's weather report found two crashes in the last week on master during the new-threads-dont-join

https://jenkins.mono-project.com/job/test-mono-mainline-linux/label=debian-8-armhf/1906/testReport/MonoTests/sgen-regular-tests-ms/sgen_new_threads_dont_join_stw_exe/
https://jenkins.mono-project.com/job/test-mono-mainline-linux/label=debian-8-armhf/1896/testReport/MonoTests/sgen-regular-tests-ms/sgen_new_threads_dont_join_stw_exe/

...which have stacks implicating get_generic_info_from_stack_frame, for example

Thread 2 (Thread 0xb30ff440 (LWP 1525)):
#0  0xb6e7f544 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
#1  0xb6e7e306 in waitpid () from /lib/arm-linux-gnueabihf/libpthread.so.0
#2  0x0008ac30 in mono_handle_native_crash (signal=signal@entry=0x1bff10 "SIGSEGV", ctx=ctx@entry=0xb30fe018, info=info@entry=0xb30fdf98) at mini-exceptions.c:2564
#3  0x0002d08c in mono_sigsegv_signal_handler (_dummy=11, _info=0xb30fdf98, context=0xb30fe018) at mini-runtime.c:2870
#4  0xb6d7fb00 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
#5  0x000882d6 in get_generic_info_from_stack_frame (ji=ji@entry=0xb402b548, ctx=ctx@entry=0xb30fe470) at mini-exceptions.c:679
#6  0x0008a62e in mono_handle_exception_internal_first_pass (non_exception=0x0, out_prev_ji=<synthetic pointer>, out_ji=<synthetic pointer>, out_filter_idx=<synthetic pointer>, obj=0xb69b7590, ctx=0xb30fe470) at mini-exceptions.c:1558

If this is the line I think it is, this could be caused if jinfo_get_method returns NULL?

Note You need to log in before you can comment on or make changes to this bug.