From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tips debugging fs
Date: Sat, 25 Feb 2006 13:30:39 -0500 [thread overview]
Message-ID: <1593dc418e80c25400c8880ff035c816@swtch.com> (raw)
In-Reply-To: <82c890d00602250836i1c20e383na1db3bbc46f5e283@mail.gmail.com>
If the process is not calling exits,
then the broken process should still
be around and debuggable.
ps | grep Broken
and then run acid on that pid.
Running leak on a program should
not change its behavior (it doesn't even
stop the program), so I don't think that's
causing the crash.
Russ
next prev parent reply other threads:[~2006-02-25 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 16:36 Gabriel Diaz
2006-02-25 18:30 ` Russ Cox [this message]
2006-02-25 18:37 ` andrey mirtchovski
2006-02-25 18:53 ` Gabriel Diaz
2006-02-25 18:56 ` Russ Cox
2006-02-25 19:08 ` Gabriel Diaz
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=1593dc418e80c25400c8880ff035c816@swtch.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).