Bug 8569 - Assertion at mono-debug.c:201, condition `table' not met
Summary: Assertion at mono-debug.c:201, condition `table' not met
Status: RESOLVED DUPLICATE of bug 4595
Alias: None
Product: Runtime
Classification: Mono
Component: Debugger ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-11-23 10:04 UTC by Andres G. Aragoneses
Modified: 2013-04-12 13:48 UTC (History)
4 users (show)

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

Stack traces from crash (12.86 KB, text/plain)
2013-01-24 10:24 UTC, Weeble
osx nunit crash (9.08 KB, text/plain)
2013-03-26 00:16 UTC, James Cline

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 Andres G. Aragoneses 2012-11-23 10:04:19 UTC
I just got this segmentation fault while running NUnit with Mono 2.11.3.

I know this bug report may not be very useful, but it's better than nothing:

[15:00:59][Step 2/4]
[15:00:59][Step 2/4]
[15:00:59][Step 2/4] * Assertion at mono-debug.c:201, condition `table' not met
[15:00:59][Step 2/4]
[15:00:59][Step 2/4] Stacktrace:
[15:00:59][Step 2/4] NUnit report watcher
[15:00:59][Step 2/4]
[15:00:59][Step 2/4]
[15:00:59][Step 2/4] Native stacktrace:
[15:00:59][Step 2/4]
[15:00:59][Step 2/4] /usr/bin/mono() [0x496916]
[15:00:59][Step 2/4] /lib/libpthread.so.0(+0xeff0) [0x7f204fc04ff0]
[15:00:59][Step 2/4] /lib/libc.so.6(gsignal+0x35) [0x7f204f8c61b5]
[15:00:59][Step 2/4] /lib/libc.so.6(abort+0x180) [0x7f204f8c8fc0]
[15:00:59][Step 2/4] /usr/bin/mono() [0x5e422b]
[15:00:59][Step 2/4] /usr/bin/mono() [0x5e42d7]
[15:00:59][Step 2/4] /usr/bin/mono() [0x4fac16]
[15:00:59][Step 2/4] /usr/bin/mono(mono_debug_remove_method+0x3e) [0x4fb63e]
[15:00:59][Step 2/4] /usr/bin/mono() [0x416c73]
[15:00:59][Step 2/4] /usr/bin/mono() [0x53f942]
[15:00:59][NUnit report watcher] Watching paths:
[15:00:59][NUnit report watcher] /srv/Teamcity/work/27d6dd15b01f232a/src/SevenDigital.Api.TrackOwnership.Unit.Tests/bin/Release/SevenDigital.Api.TrackOwnership.Unit.Tests.xml
[15:00:59][Step 2/4] /usr/bin/mono() [0x548c00]
[15:00:59][Step 2/4] /usr/bin/mono() [0x55fdc6]
[15:00:59][Step 2/4] /usr/bin/mono() [0x55fe00]
[15:00:59][Step 2/4] /usr/bin/mono() [0x561181]
[15:00:59][Step 2/4] /usr/bin/mono() [0x5166ba]
[15:00:59][Step 2/4] /usr/bin/mono() [0x5c2ed3]
[15:00:59][Step 2/4] /usr/bin/mono() [0x5d58f9]
[15:00:59][Step 2/4] /usr/bin/mono() [0x5f9147]
[15:00:59][Step 2/4] /lib/libpthread.so.0(+0x68ca) [0x7f204fbfc8ca]
[15:00:59][Step 2/4] /lib/libc.so.6(clone+0x6d) [0x7f204f963b6d]
[15:00:59][Step 2/4]
[15:00:59][Step 2/4] Debug info from gdb:
[15:00:59][Step 2/4]
[15:00:59][Step 2/4]
[15:00:59][Step 2/4] =================================================================
[15:00:59][Step 2/4] Got a SIGABRT while executing native code. This usually indicates
[15:00:59][Step 2/4] a fatal error in the mono runtime or one of the native libraries
[15:00:59][Step 2/4] used by your application.
[15:00:59][Step 2/4] =================================================================
[15:00:59][Step 2/4]
[15:00:59][Step 2/4] Aborted
Comment 1 Zoltan Varga 2012-11-24 05:22:12 UTC
The assertion seems familiar, but we could never reproduce it.
Comment 2 Andres G. Aragoneses 2012-11-24 09:58:59 UTC
I have the suspicion it happened in circumstances of exceptional lack of free memory.
Comment 3 Weeble 2013-01-24 10:24:22 UTC
Created attachment 3280 [details]
Stack traces from crash

I observed this today. I got a slightly more descriptive stack trace from the crash, which I've attached. Hope that helps.
Comment 4 James Cline 2013-03-26 00:16:24 UTC
Created attachment 3694 [details]
osx nunit crash

I can reproduce this frequently on OSX 10.7.5 with Mono 2.10.12 (mono-2-10/c9b270d). It does not happen 100% of the time, but with a short running test I can typically hit it every 1-3 runs.
Comment 5 Zoltan Varga 2013-03-26 00:35:50 UTC
Could you try creating a test case which reproduces this problem ?
Comment 6 Eric Fikus 2013-04-12 13:36:04 UTC
Looks like this was also filed at #4595
Comment 7 Andres G. Aragoneses 2013-04-12 13:48:27 UTC

*** This bug has been marked as a duplicate of bug 4595 ***