Bug 13414 - JIT crash in mono_arch_find_jit_info
Summary: JIT crash in mono_arch_find_jit_info
Status: RESOLVED NORESPONSE
Alias: None
Product: Runtime
Classification: Mono
Component: JIT ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-07-23 11:00 UTC by Mikayla Hutchinson [MSFT]
Modified: 2017-07-07 21:01 UTC (History)
4 users (show)

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


Attachments
Full crash trace (26.88 KB, text/plain)
2013-07-23 11:02 UTC, Mikayla Hutchinson [MSFT]
Details
gdb t a a bt (17.24 KB, text/plain)
2013-07-23 11:04 UTC, Mikayla Hutchinson [MSFT]
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Mikayla Hutchinson [MSFT] 2013-07-23 11:00:28 UTC
When opening MonoDevelop's Main.sln in Mono master, I get the following hard crash in the JIT:

Thread 1 (process 79919):
#0  0x92ecd09a in __wait4 ()
#1  0x915f6996 in waitpid$UNIX2003 ()
#2  0x00154382 in mono_handle_native_sigsegv (signal=11, ctx=0x763fe0) at mini-exceptions.c:2344
#3  0x001a3d95 in mono_arch_handle_altstack_exception (sigctx=0x763fe0, fault_addr=0x18a0, stack_ovf=0) at exceptions-x86.c:1135
#4  0x000af421 in mono_sigsegv_signal_handler (_dummy=10, info=0x763fa0, context=0x763fe0) at mini.c:6559
#5  <signal handler called>
#6  mono_arch_find_jit_info (domain=0x7b6403b0, jit_tls=0x7b656e70, ji=0xbff541d8, ctx=0xbff54428, new_ctx=0xbff542e8, lmf=0xbff54338, save_locations=0x0, frame=0xbff542b8) at exceptions-x86.c:804
#7  0x00152b9e in mono_find_jit_info_ext (domain=0x7b6403b0, jit_tls=0x7b656e70, prev_ji=0x0, ctx=0xbff54428, new_ctx=0xbff542e8, trace=0x0, lmf=0xbff54338, save_locations=0x0, frame=0xbff542b8) at mini-exceptions.c:376
#8  0x001533a7 in mono_handle_exception_internal_first_pass (ctx=0xbff54348, obj=0xbff54348, out_filter_idx=0xbff5444c, out_ji=0xbff54458, out_prev_ji=0xbff54454, non_exception=0x0) at mini-exceptions.c:1342
#9  0x00154dd9 in mono_handle_exception_internal () at mini-exceptions.c:2450
#10 0x00155939 in mono_handle_exception (ctx=0xbff544d8, obj=0x9af1e0) at mini-exceptions.c:1972
#11 0x001a4dcd in mono_x86_throw_exception (regs=0xbff54520, exc=0x9af1e0, eip=335185304, rethrow=0) at exceptions-x86.c:465
Comment 1 Mikayla Hutchinson [MSFT] 2013-07-23 11:02:16 UTC
Created attachment 4402 [details]
Full crash trace
Comment 2 Mikayla Hutchinson [MSFT] 2013-07-23 11:04:53 UTC
Created attachment 4404 [details]
gdb t a a bt
Comment 3 Zoltan Varga 2013-07-23 12:17:46 UTC
Reverted a problematic commit. Could you try again with master ?
Comment 4 Zoltan Varga 2013-09-05 11:29:01 UTC
-> NEEDINFO.
Comment 5 Ludovic Henry 2017-07-07 21:01:51 UTC
Can you still reproduce this bug with latest version of mono? Please feel free to reopen if that is still the case. Thank you.