Mailinglist Archive: opensuse (1468 mails)

< Previous Next >
Re: [opensuse] gdb/corefile question
  • From: Philipp Thomas <Philipp.Thomas2@xxxxxxx>
  • Date: Wed, 03 Jun 2009 00:40:57 +0200
  • Message-id: <2f9b25hfv7bbuk47k7j6lphj3257br4esg@xxxxxxx>
On Tue, 2 Jun 2009 20:45:40 +0000 (UTC), you wrote:

What other options do I have to get a core from this program?

One option would be to run the program under catchsegv (i.e. catchsegv
<your_prog>). For catchsegv to give meaningfull backtraces, you should have
the -debuginfo packages of that program (if it comes from a SUSE package)
installed or have a non-stripped binary with debugging info. To really
help, you should also install the -debuginfo packages for all involved
libraries (i.e. glibc at the very least).

Your problem could stem from the fact that the memory layout when running
under gdb is sufficiently different to not cause a segfault. In that case,
I'd try running the program under valgrind.

If you have the sources for the program, I'd try adding -D_FORTIFY_SOURCE=2
and -fstack-protector to the compiler flags (if they've been written in C
and/or C++).

You might also get better help on the opensuse-programming mailing list.

Philipp
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References