Ubuntu
mono package

All mono apps crash with a "Got a SIGSEGV while executing native code." message.

Bug #42059 reported by Pierre Buyle on 2006-04-29

10

Affects		Status	Importance	Assigned to	Milestone
	mono (Ubuntu)	Invalid	Medium	Sebastian Dröge

Bug Description

Hi,

since I updated my Dapper Box, all mono apps dies because of a SIGSEGV in native code execution. For instance, here is the ouput of muine:
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Stacktrace:

Native stacktrace:

        /usr/lib/libmono.so.0(mono_handle_native_sigsegv+0xe3) [0x4008b43f]
        /usr/lib/libmono.so.0 [0x4004d03e]
        /lib/libpthread.so.0 [0x48dd65ca]
        [0xffffe440]
        [0x40a8da82]
        [0x40a8da21]
        [0x40a8d66b]
        [0x40a81eae]
        /usr/lib/libmono.so.0 [0x4006a438]
        /usr/lib/libmono.so.0(mono_runtime_invoke+0x33) [0x400cceed]
        /usr/lib/libmono.so.0(mono_runtime_class_init+0x13f) [0x400cf12f]
        /usr/lib/libmono.so.0 [0x4006a16e]
        /usr/lib/libmono.so.0(mono_compile_method+0x24) [0x400cd225]
        /usr/lib/libmono.so.0(mono_magic_trampoline+0x1f) [0x400a1b1f]
        [0x402ed032]
        [0x40a8d2fa]
        [0x40a8d299]
        [0x40a8b3d4]
        [0x40a8b346]
        [0x40a8acec]
        [0x40a8791d]
        [0x40a81823]
        /usr/lib/libmono.so.0 [0x4006a438]
        /usr/lib/libmono.so.0(mono_runtime_invoke+0x33) [0x400cceed]
        /usr/lib/libmono.so.0(mono_runtime_exec_main+0x67) [0x400cfa88]
        /usr/lib/libmono.so.0(mono_runtime_run_main+0x188) [0x400d2bf0]
        /usr/lib/libmono.so.0(mono_jit_exec+0x90) [0x4007cb5e]
        /usr/lib/libmono.so.0(mono_main+0x962) [0x4007d54f]
        /lib/libc.so.6(__libc_start_main+0xa3) [0x48c8731f]
        /usr/bin/mono [0x8048459]

I tried to "apt-get reinstall" libmono0 and several other mono related packages but without any result.

Revision history for this message

sam tygier (samtygier) wrote on 2006-04-29:

#1

looks like Bug #33826, which is marked fix released. are you up to date?

Revision history for this message

Pierre Buyle (mongolito404) wrote on 2006-04-29:

#2

Yes, to be sure, I tried "apt-get update" and "apt-get [dist-]upgrade" right now and no update are available.

I only use packages from officials dapper repositories, no third-party repositories or hand compiled packages.

Revision history for this message

Sebastian Dröge (slomo) wrote on 2006-04-30:

#3

Ok, let's get a small testcase together...
please try to run the two attached testcases and paste any output here

Revision history for this message

Sebastian Dröge (slomo) wrote on 2006-04-30: test1.exe

#4

test1.exe Edit (3.0 KiB, application/x-msdos-program)

test1.exe

Revision history for this message

Sebastian Dröge (slomo) wrote on 2006-04-30: test2.exe

#5

test2.exe Edit (3.0 KiB, application/x-msdos-program)

test2.exe

Changed in mono:
assignee:	nobody → slomo
status:	Unconfirmed → Needs Info

Revision history for this message

Pierre Buyle (mongolito404) wrote on 2006-04-30:

#6

$ ./test1.exe
foo

and then nothing, it doesn't finish and outputs nothing more.

$ ./test2.exe
foo7038

and again nothing, it doesn't finish and outputs nothing more.

Revision history for this message

Sebastian Dröge (slomo) wrote on 2006-04-30:

#7

It doesn't exit at all? Weird... at least now we know that your problem is not related to executing native code... the second testfile does that.

Do you have the problem with really all mono applications? When exactly does it happen? Already at start?

Revision history for this message

Pierre Buyle (mongolito404) wrote on 2006-04-30:

#8

No, test1 et test2 don't exit at all.

I've the same problem ("Got a SIGSEGV while executing native code.") with muine, f-spot, beagle-search, banshee and monodevelop. Should I copy/paster their outputs ?

Revision history for this message

Pierre Buyle (mongolito404) wrote on 2006-04-30:

#9

Sorry, I forgot to confirm that yes, it happens right at the start, it's almost instantly.

Revision history for this message

Sebastian Dröge (slomo) wrote on 2006-04-30:

#10

Could you run
strace -o log mono ./test1.exe

and attach the file named log from that directory here? Just exit the program with ctrl+c

Revision history for this message

Pierre Buyle (mongolito404) wrote on 2006-04-30: strace -o log mono ./test1.exe

#11

strace -o log mono ./test1.exe Edit (47.0 KiB, text/plain)

Here is the result of my "strace -o log mono ./test1.exe"

Revision history for this message

Sebastian Dröge (slomo) wrote on 2006-04-30:

#12

Ok there is something really broken...
Can you tell me something about your platform? What type of CPU etc

Revision history for this message

Pierre Buyle (mongolito404) wrote on 2006-05-01:

#13

My CPU is an AMD Athlon XP 1800+ running on a Mercury KOB KT266a FDSX motherboard with 2 x 512Mb of unbranded RAM, an old nvidia GeForce 2 Ti (NV15DDR rev a4), a Compaq Netelligent 10/100 TX PCI network device, an old PCI Bt8787 TV card and an USB 2.0 + Firewire PCI card.

My system is an up-to-date Dapper upgraded from a Breezy wich was itself upgraded from an Hoary.

I can give more specific info if you want, just tell me what.

Revision history for this message

Sebastian Dröge (slomo) wrote on 2006-05-01:

#14

Can someone else confirm this behaviour? I have absolutely no clue what could be wrong here...

Changed in mono:
status:	Needs Info → Confirmed
status:	Confirmed → Unconfirmed

Revision history for this message

Pierre Buyle (mongolito404) wrote on 2006-05-03:

#15

When I use the Dapper Beta2 LiveCD, mono apps works great.

Revision history for this message

Sebastian Dröge (slomo) wrote on 2006-05-03:

#16

That's weird... and if you install from beta2 everything falls apart?
Because beta2 has exactly the same mono stuff as we had at the time of your bug report

Revision history for this message

Pierre Buyle (mongolito404) wrote on 2006-05-04:

#17

I've also a "bug" with libwxgtk2.6 on my system that doesn't show up with the LiveCD. Something must be wrong on my system but I don't know what. As soon as I've the time for it, I plan to trie to apt-get re-install all packages on wich mono depends.

This bug could probably be closed, if something went wrong when I upgraded it's probably not in the mono package.

Thanks for your work.

Revision history for this message

Pierre Buyle (mongolito404) wrote on 2006-05-05:

#18

I apt-get reinstall libc6 libglib2.0-0 and libmono-1.1.13.6, muine now works and test(1|2).exe exits all right.

Again, thank you for your time.

Sebastian Dröge (slomo) on 2006-05-06

Changed in mono:
status:	Unconfirmed → Rejected

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.