[Mono-list] Re: Garbage collection and memory usage

[Georgi Moskov]

Hello,

I will skip the comppression, since the output is not so big ...

  9 Thread -1219900496 (LWP 2849)  0xb7c966c6 in semop ()
   from /lib/tls/libc.so.6
  8 Thread -1219982416 (LWP 2879)  0xb7d22440 in
pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0
  7 Thread -1223263312 (LWP 2881)  0xb7c966c6 in semop ()
   from /lib/tls/libc.so.6
  6 Thread -1229239376 (LWP 2912)  0xb7d22440 in
pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/libpthread.so.0
  5 Thread -1230496848 (LWP 2913)  0xb7d24dfc in __nanosleep_nocancel ()
   from /lib/tls/libpthread.so.0
  4 Thread -1234740304 (LWP 2921)  0xb7c966c6 in semop ()
   from /lib/tls/libc.so.6
  3 Thread -1224311888 (LWP 3172)  0xb7c966c6 in semop ()
   from /lib/tls/libc.so.6
  2 Thread -1233683536 (LWP 3231)  0xb7c966c6 in semop ()
   from /lib/tls/libc.so.6
  1 Thread -1212431040 (LWP 2809)  0xb7c966c6 in semop ()
   from /lib/tls/libc.so.6

Thread 9 (Thread -1219900496 (LWP 2849)):

Program received signal SIGSEGV, Segmentation fault.
0xb7ec6e39 in mono_jit_info_table_find () from /usr/lib/libmono.so.0
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on"
Evaluation of the expression containing the function (mono_pmip) will
be abandoned.
#0  0xb7c966c6 in semop () from /lib/tls/libc.so.6

This happens at  "t a a mono_backtrace 100", with or without "set
unwindonsignal on".

Regards,
Georgi Moskov