Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Kaz Kylheku <kaz@kylheku.com> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: Error handling |
| Date | 2011-11-05 15:31 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <20111105083216.546@kylheku.com> (permalink) |
| References | <j93dqr$d4u$1@speranza.aioe.org> |
On 2011-11-05, t1t0 <t1t0@noemail.not> wrote: > Hi all, > > there is a good way to obtain the 'call stack' when errors occur ? > > On Linux the S.O. create a core dump file with the debug information, but > I would like to have a similar information inside the program, to log > ever the error and send for an application/email/etc. On glibc-based Linux, you have a function called backtrace.
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Error handling t1t0 <t1t0@noemail.not> - 2011-11-05 13:31 +0000
Re: Error handling Eric Sosman <esosman@ieee-dot-org.invalid> - 2011-11-05 09:55 -0400
Re: Error handling t1t0 <t1t0@noemail.not> - 2011-11-05 18:37 +0000
Re: Error handling Eric Sosman <esosman@ieee-dot-org.invalid> - 2011-11-05 14:50 -0400
Re: Error handling t1t0 <t1t0@noemail.not> - 2011-11-06 10:36 +0000
Re: Error handling Kaz Kylheku <kaz@kylheku.com> - 2011-11-06 01:15 +0000
Re: Error handling t1t0 <t1t0@noemail.not> - 2011-11-06 10:44 +0000
Re: Error handling Nick Keighley <nick_keighley_nospam@hotmail.com> - 2011-11-06 06:02 -0800
Re: Error handling Kaz Kylheku <kaz@kylheku.com> - 2011-11-06 16:21 +0000
Re: Error handling Nobody <nobody@nowhere.com> - 2011-11-05 14:10 +0000
Re: Error handling Kaz Kylheku <kaz@kylheku.com> - 2011-11-05 15:31 +0000
Re: Error handling Mike Manilone <zhtx10@gmail.com> - 2011-11-06 03:56 +0000
csiph-web