From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Redondo Garcia, Roberto" <rredondo@indra.es>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: back trace when a SIGSEGV
Date: Mon, 05 Dec 2005 09:16:02 +1100 [thread overview]
Message-ID: <1133734562.6100.104.camel@gaston> (raw)
In-Reply-To: <6A28467355D2AD478D1F51C479415AE77B47E9@MADTORMAIL.indra.es>
On Fri, 2005-12-02 at 11:33 +0100, Redondo Garcia, Roberto wrote:
> hello,
> I have a program that when it has been several hours running, it has a
> problem and falls and it produces a SIGSEGV. I would like to know to
> how debug this error, because I do not have ulimit for generate core
> dump o examine a back trace.
You can run your program under gdb, or you may want to have a look at
tridge' junk code directory for his segv_handler bit that you can put in
LD_PRELOAD
http://www.samba.org/junkcode/#segv_handler
Ben.
next prev parent reply other threads:[~2005-12-04 22:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 10:33 back trace when a SIGSEGV Redondo Garcia, Roberto
2005-12-02 14:27 ` Dustin Lang
2005-12-04 22:14 ` Benjamin Herrenschmidt
2005-12-05 1:20 ` Dustin Lang
2005-12-05 1:23 ` Benjamin Herrenschmidt
2005-12-02 15:35 ` Wolfgang Denk
2005-12-04 22:16 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-17 10:29 Redondo Garcia, Roberto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1133734562.6100.104.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rredondo@indra.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.