From: Wolfgang Denk <wd@denx.de>
To: "Redondo Garcia, Roberto" <rredondo@indra.es>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: back trace when a SIGSEGV
Date: Fri, 02 Dec 2005 16:35:52 +0100 [thread overview]
Message-ID: <20051202153552.49244353A14@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 02 Dec 2005 11:33:46 +0100." <6A28467355D2AD478D1F51C479415AE77B47E9@MADTORMAIL.indra.es>
In message <6A28467355D2AD478D1F51C479415AE77B47E9@MADTORMAIL.indra.es> you wrote:
>
> 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.
Run the program under control of a debugger (gdb, or - if you're on a
resource-limited target - gdbserver).
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Es ist nicht genug zu wissen, man muß auch anwenden; es ist nicht ge-
nug zu wollen, man muß auch tun. -- Goethe, Maximen und Reflexionen
next prev parent reply other threads:[~2005-12-02 15:35 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 [this message]
2005-12-04 22:16 ` Benjamin Herrenschmidt
-- 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=20051202153552.49244353A14@atlas.denx.de \
--to=wd@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).