Has someone experiences with the GNU debugger applied to cm3 compiled
programs? GDB can be of big help when backtracing some nested function
calls. I have a program which raises an exception, but when run under GDB
it aborts even earlier, so I cannot trace the exception of interest. :-(
thielema@[EMAIL PROTECTED]
> cm3 -version
Critical Mass Modula-3 version 5.2.6
last updated: 2003-06-27
configuration: /home/thielema/cm3/bin/LINUXLIBC6/cm3.cfg
thielema@[EMAIL PROTECTED]
> gdb LINUXLIBC6/test
GNU gdb Red Hat Linux (5.2-2)
....
(gdb) run
Starting program:
/home/thielema/programming/m3/pkg/wavelib/test/LINUXLIBC6/test
Program received signal SIGSEGV, Segmentation fault.
0x400205fa in LongRealSignal__Init (M3_EYFkVD_SELF=0x403c3208,
M3_AcxOUs_first=-512, M3_AcxOUs_number=1149) at Signal.mg:50
50 Signal.mg: No such file or directory.
in Signal.mg
(gdb) backtrace
#0 0x400205fa in LongRealSignal__Init (M3_EYFkVD_SELF=0x403c3208,
M3_AcxOUs_first=-512, M3_AcxOUs_number=1149) at Signal.mg:50
#1 0x4002114b in LongRealSignal__UpSample (M3_EYFkVD_x=0x403c31f8,
M3_AcxOUs_factor=2) at Signal.mg:184
....
LongRealSignal is a SAFE module and should not make any troubles I
thought.
|
