A core file won't get created if you run pidgin inside gdb. Please describe the steps you took to get pidgin to crash, and attach the output of running pidgin -d outside of gdb. Then try moving your ~/.purple directory out of the way and try again. Lastly, if pidgin still crashes, please try running it inside gdb by following the directions here: http://wiki.debian.org/HowToGetABacktrace Don't worry about the "no debugging symbols" messages.
On Wed, 2007-09-05 at 14:30 +0100, Matthew Tylee Atkinson wrote: > Package: pidgin > Version: 2.0.1-1 > Severity: important > > I have followed the advice in the BTS to install the following packages: > libglib2.0-0-dbg; > libgtk2.0-0-dbg and pidgin-dbg. However, when I try to run pidgin -d or > pidgin from within > gdb, the core file created seems to have no debuging symbols in it. dgb > says: ``(no > debugging symbols found)''. I have also run ``ulimit -c unlimited'' from the > terminal and > have had no luck. > > I don't think I will be able to provide any useful information until I can > get the backtrace > to work but I have tried the current unstable version of pidgin (2.1.1) and > it still crashes > at some point early after startup. > > If you could help me try to work out why the debugging symbols are not being > used, that > would be of great help. > > best regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
