From: David Carlton <carlton@kealia.com>
To: gdb <gdb@sources.redhat.com>
Subject: generating a core file
Date: Mon, 22 Mar 2004 17:52:00 -0000 [thread overview]
Message-ID: <yf2lllsu75w.fsf@hawaii.kealia.com> (raw)
This is quite off-topic, but are there any programs out there that can
generate a core file from a stopped process, and write that core file
to a pipe or send it over the network somehow? We're having issues
debugging seg faults on machines without local disks, and for various
reasons we'd rather not remotely mount disks on these machines,
either.
David Carlton
carlton@kealia.com
next reply other threads:[~2004-03-22 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 17:52 David Carlton [this message]
2004-03-22 18:17 ` Kip Macy
2004-03-22 19:17 ` David Carlton
2004-03-22 20:59 ` Daniel Jacobowitz
2004-03-23 1:27 ` Kip Macy
2004-03-23 9:55 ` Andrew Cagney
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=yf2lllsu75w.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=gdb@sources.redhat.com \
/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