traceback:
#0 0x402179d4 in mallopt () from /lib/libc.so.6
#1 0x40216b61 in malloc () from /lib/libc.so.6
#2 0x401524ae in operator new(unsigned) () from /usr/lib/libstdc++.so.5
#3 0x401525ff in operator new[](unsigned) () from /usr/lib/libstdc++.so.5
#4 0x0805de2c in Buffer::set(char const*) (this=0xbffff8c0, p=0x8064f90
".mailfilter") at buffer.C:34
#5 0x080507df in run (argc=1, argv=0xbffff964) at buffer.h:55
#6 0x08051ea5 in main (argc=1, argv=0xbffff964) at main.C:1118
#7 0x401ba80c in __libc_start_main () from /lib/libc.so.6
English:
???
Is there a way of obtaining traceback of a correctly excecuting program.
EG. a traceback of maildrop -h?
Thanks,
Rob
-----Original Message-----
From: cour...@lists.sourceforge.net
[mailto:cour...@lists.sourceforge.net]On Behalf Of Sam
Varshavchik
Sent: Saturday, August 23, 2003 8:34 PM
To: cour...@lists.sourceforge.net
Subject: [maildropl] Re: Working on patch to autocreate maildirs/off
topic
Rob Hutton writes:
OK. Is there any way in the signal handler to figure out what line the
SIG11 came from?
Yes: dump core and let the debugger obtain the stack backtrace.
17 messages in net.sourceforge.lists.courier-maildropRE: [maildropl] Re: Working on patch ...
