Re: Xchat segfault - privmsg or ctcp...

[Richard Fuchs <dfx@gmx.at>]

On Fri, Jun 08, 2001 at 11:22:23AM +1000, Troy Bell wrote:
> Carsten Bauer wrote:
> > Ok, i was on another desktop at the time, so dont know what caused it.
> > 
> > I heard a beep, like it was a privmsg or a ctcp.. got the segfault warning 
> > box come up....
> > 
> > Looked in the logfiles for a reason, but cannoy find it.
> > Last command i ran was
> > 
> > /CTCP #Perthpeoples SHUTTUP-MARKUS
> > 
> > very weird...
> 
> If it keeps happening... maybe running 'strace xchat' might give you
> some decent output that might identify the problem when it does
> segfault.

Better yet, if you want to report occasional segfaults without having to
run xchat (or other progs) through gdb all the time, enable core dumps (on
linux boxes they're usually disabled by default). You can do this by running
the command "ulimit -c unlimited" (for bash), then start xchat from the same
shell. You can even put that command into your ~/.profile, so you have core
dumps enabled all the time. Programs will then leave a core file when they
segfault, which you can load into gdb and so look at the backtrace, for
example with "gdb /usr/bin/xchat ~/core".

Richard
-
XChat-discuss: mailing list for XChat users
Archive:       http://mail.nl.linux.org/xchat-discuss/
Posted By:     Richard Fuchs <dfx@gmx.at>