[M3devel] m3gdb crashing

Dragiša Durić dragisha at m3w.org
Fri Mar 21 16:51:11 CET 2008


(gdb) bt
#0  0x00110402 in __kernel_vsyscall ()
#1  0x43341a3e in __lll_mutex_lock_wait () from /lib/libpthread.so.0
#2  0x4333d890 in _L_mutex_lock_85 () from /lib/libpthread.so.0
#3  0x4333d3dd in pthread_mutex_lock () from /lib/libpthread.so.0
#4  0x002f5003 in Thread__Acquire (M3_AYIbX3_m=0xb7f31960)
at ../src/thread/PTHREAD/ThreadPThread.m3:143
#5  0x08049c61 in Connection__Append (M3_DlOx9a_b=0xb7f31960,
M3_CKMnXU_pkt=0xbfd57034, M3_AicXUJ_signal=1 '\001')
    at ../src/Connection.m3:138
#6  0x0804c044 in PDU__Send (M3_DzQGng_b=0xb7526b58,
M3_ALzNrn_c=0xb7f31900) at ../src/PDU.m3:124
#7  0x0804d802 in SMPP_M3 (M3_AcxOUs_mode=1) at ../src/SMPP.m3:200
#8  0x002e1032 in RTLinker__RunMainBody (M3_DjPxE3_m=0x804fa80)
at ../src/runtime/common/RTLinker.m3:399
#9  0x002df92c in RTLinker__AddUnitI (M3_DjPxE3_m=0x804fa80)
at ../src/runtime/common/RTLinker.m3:113
#10 0x002df9c3 in RTLinker__AddUnit (M3_DjPxE5_b=0x804d3df)
at ../src/runtime/common/RTLinker.m3:122
#11 0x080493d8 in main (argc=1, argv=0xbfd57314, envp=0xbfd5731c) at
_m3main.mc:4

This is output from regular gdb, it works.

If it's important, this is piece of code...

PROCEDURE Send(b: T; c: Connection.T) =
  BEGIN
    SetInt(b, 0, 4, b.used);
    LOCK c.output DO
      INC(c.seq);
      SetInt(b, 12, 4, c.seq);
      c.output.append(SUBARRAY(b.data^, 0, b.used));
    END;
  END Send;

  My bug was... append method also tries to lock c.output... It is a
moment when I Ctrl-C-ed it.

dd

On Fri, 2008-03-21 at 09:42 -0400, Tony Hosking wrote:
> Does it work with regular gdb?
> 
> On Mar 21, 2008, at 4:28 AM, Dragiša Durić wrote:
> 
> > Program received signal SIGINT, Interrupt.
> > [Switching to Thread -1208531264 (LWP 20589)]
> > 0x00110402 in __kernel_vsyscall ()
> > (m3gdb) bt
> > #0  0x00110402 in __kernel_vsyscall ()
> > #1  0x43341a3e in __lll_mutex_lock_wait () from /lib/libpthread.so.0
> > #2  0x4333d890 in _L_mutex_lock_85 () from /lib/libpthread.so.0
> > ../../gdb/gdb/dwarf2-frame.c:490: internal-error: Unknown CFI
> > encountered.
> > A problem internal to GDB has been detected,
> > further debugging may prove unreliable.
> >
> > -- 
> > Dragiša Durić <dragisha at m3w.org>
> 
-- 
Dragiša Durić <dragisha at m3w.org>




More information about the M3devel mailing list