Bug 55936 - pedump crashes on coop Intel32 lane
Summary: pedump crashes on coop Intel32 lane
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Aleksey Kliger
Depends on:
Reported: 2017-05-03 21:02 UTC by Andi McClure
Modified: 2017-05-04 14:04 UTC (History)
2 users (show)

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

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:

Description Andi McClure 2017-05-03 21:02:09 UTC
If you look at our Intel32 coop lane


It fails consistently with an error in pedump


MONO_PATH=/mnt/jenkins/workspace/test-mono-mainline-coop/label/ubuntu-1404-i386/mcs/class/lib/net_4_x /mnt/jenkins/workspace/test-mono-mainline-coop/label/ubuntu-1404-i386/tools/pedump/pedump --verify error test-runner.exe
make[4]: *** [test-pedump] Segmentation fault (core dumped)

Aleksey was able to reproduce locally

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt
#0  0x00000000 in ?? ()
#1  0x081a1320 in mono_threads_enter_gc_safe_region_unbalanced_with_info (info=info@entry=0x8312e18, 
    stackdata=stackdata@entry=0xbfffef2c) at mono-threads-coop.c:242
#2  0x081a137d in mono_threads_enter_gc_safe_region_with_info (info=0x8312e18, stackdata=0xbfffef2c)
    at mono-threads-coop.c:212
#3  0x0819c304 in mono_thread_info_suspend_lock_with_info (info=0x8312e18) at mono-threads.c:1036
#4  0x0819de8b in register_thread (baseptr=<optimized out>, info=<optimized out>) at mono-threads.c:403
#5  mono_thread_info_attach (baseptr=0xbfffef90) at mono-threads.c:621
#6  0x08131bcc in mono_gc_register_thread (baseptr=0xbfffef88) at sgen-mono.c:2322
#7  sgen_client_init () at sgen-mono.c:2908
#8  0x081627b5 in sgen_gc_init () at sgen-gc.c:3068
#9  0x08131ef2 in mono_gc_base_init () at sgen-mono.c:3024
#10 0x080f9782 in mono_init_internal (filename=0x830ee80 <runtime_callbacks> "", 
    filename@entry=0x81b48ce "pedump", exe_filename=0x0, runtime_version=0x8312688 "v4.0.30319")
    at domain.c:505
#11 0x080fa34f in mono_init_version (domain_name=0x81b48ce "pedump", version=0x8312688 "v4.0.30319")
    at domain.c:827
#12 0x080512fa in verify_image_file (fname=<optimized out>) at pedump.c:466
#13 main (argc=4, argv=0xbffff2f4) at pedump.c:709
Comment 1 Aleksey Kliger 2017-05-03 21:38:51 UTC
Yea it's an initialization problem.  Fix is the same as https://github.com/mono/mono/commit/9f5115a343213e7ce27b197c96274cc611a05284 which fixed monodis
Comment 2 Aleksey Kliger 2017-05-04 14:04:38 UTC
Fixed on mono master https://github.com/mono/mono/commit/20bdb3ec834c1bad4162852d498ab52ca28271ed