From: Ralph Corderoy <ralph@inputplus.co.uk>
To: coff@tuhs.org
Subject: [COFF] Conditions, AKA exceptions.
Date: Sat, 11 Mar 2023 11:28:49 +0000 [thread overview]
Message-ID: <20230311112849.22C0920145@orac.inputplus.co.uk> (raw)
In-Reply-To: <20230310174222.GB9225@mcvoy.com>
Hi Larry,
> cmd = aprintf("gdb -batch -ex backtrace '%s/bk' %u 1>&%d 2>&%d",
> bin, getpid(), fileno(f), fileno(f));
>
> system(cmd);
I also came up with this, probably on an SGI Iris Indigo, and got it
added to the Unix Programming FAQ. :-)
6.5 How can I generate a stack dump from within a running program?
http://www.faqs.org/faqs/unix-faq/programmer/faq/
It works surprisingly often, i.e. the process is healthy enough to run
system(3).
--
Cheers, Ralph.
next prev parent reply other threads:[~2023-03-11 11:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:11 [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Bakul Shah
2023-03-10 17:28 ` segaloco via COFF
2023-03-10 17:34 ` Larry McVoy
2023-03-10 17:35 ` Bakul Shah
2023-03-10 17:42 ` Larry McVoy
2023-03-11 11:28 ` Ralph Corderoy [this message]
2023-03-12 4:23 ` [COFF] Re: Conditions, AKA exceptions Theodore Ts'o
2023-03-12 10:44 ` Ralph Corderoy
2023-03-12 16:46 ` Paul Winalski
2023-03-12 16:53 ` Larry McVoy
2023-03-10 17:43 ` [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) segaloco via COFF
2023-03-10 18:03 ` Dan Cross
2023-03-10 18:57 ` Bakul Shah
2023-03-10 19:57 ` Marshall Conover
2023-03-13 16:47 ` [COFF] Conditions, AKA exceptions Ralph Corderoy
2023-03-13 17:10 ` [COFF] " Paul Winalski
2023-03-13 21:12 ` Dave Horsfall
2023-03-10 17:47 ` [COFF] Re: [TUHS] Re: Conditions, AKA exceptions. (Was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Bakul Shah
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=20230311112849.22C0920145@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=coff@tuhs.org \
/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).