Re: sawfish-config segfault
- From: Allan Duncan <amd2345 fastmail com au>
- To: sawfish-list gnome org
- Subject: Re: sawfish-config segfault
- Date: Thu, 07 Jan 2010 21:30:19 +1100
On 07/01/10 09:30, Christopher Roy Bratusek wrote:
Hi all,
With the current HEADs I get a segfault when trying to launch
sawfish-config, while it didn't yesterday. But I can't see the cause
(no change in sawfish-config), can someone reproduce it? And how to get
more usefull debugging messages? Using Emacs + rep-debugger.el? Well,
I've never used Emacs.
Chris
Assuming you have core dumps enabled, start it from the command line so
you can run
"gdb -c core.nnnn" and then issue the command "backtrace". To get nicer
diagnostics you need the symbol tables etc., I'm not sure if Debian
produces the equivalent of the "debug" rpms I get. Further reading of
the gdb man page will show you how you can get the source lines relevant
to the trace as well. So long since I used that I have forgotten it all.
Beyond seeing the called parameters of the seg-faulting routine you
would need to put breakpoints on the elisp interpreter, and I not going
there.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]