On dim, 2008-09-07 at 23:16 -0400, Daniel Dickinson wrote: > On Sat, 06 Sep 2008 17:32:35 +0200 > Yves-Alexis Perez <[EMAIL PROTECTED]> wrote: > > > On sam, 2008-09-06 at 03:37 -0400, Daniel Dickinson wrote: > > > I've noticed in reviewing my syslog checking programs mails to me > > > that xfce4-places-plugin segfaults at least once per day (as > > > reported in the > > > syslog). It doesn't visibly affect anything, but is disturbing > > > nonetheless. > > > > Could you provide a complete backtrace with debugging symbols? Are you > > running sid or lenny? Could you check if you're not facing #496125 ? > > I've got the latest libxml so it's not that.
Ok. You don't do weird stuff with dbus, when that happen? > How do I get a backtrace > of a plugin, especially when I don't see the segfault, only see it in > the syslog. I know how to run a command and get a backtrace > automatically with a regular command (someone has a nice > with-gdb-backtrace-to script for that you can have wrapper script > which executes that script on the command instead of the command > directly (since /usr/local is searched before /usr)), but a plugin can't > be done the same way. You should be able to attach gdb to a running instance. Maybe you could run xfce4-panel from a terminal with limits sets to autorize coredumps, and use that core after the segfault. Cheers, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
