[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ale] How to debug a program that just goes away

Subject: [ale] How to debug a program that just goes away
From: mdhirsch at gmail.com (Michael Hirsch)
Date: Fri, 26 Feb 2010 11:53:31 -0700
In-reply-to: <[email protected]>
References: <[email protected]> <1267190530.14961.95.camel@cfowler-desktop> <[email protected]> <[email protected]>

On Fri, Feb 26, 2010 at 9:12 AM, JK <jknapka at kneuro.net> wrote:
> Also, check whether there are any core files for it.

Check that your system will leave a core file.  It is possible to
configure a system so that no core file is left.  I forget how, I'm
afraid.  But on such a system a process will just disappear after a
seg fualt with no trace.

Michael

Follow-Ups:
- [ale] How to debug a program that just goes away
  - From: lists at serioustechnology.com (Geoffrey)

References:
- [ale] How to debug a program that just goes away
  - From: ale_nospam at fayettedigital.com (Jim Lynch)
- [ale] How to debug a program that just goes away
  - From: cfowler at outpostsentinel.com (Chris Fowler)
- [ale] How to debug a program that just goes away
  - From: ale_nospam at fayettedigital.com (Jim Lynch)
- [ale] How to debug a program that just goes away
  - From: jknapka at kneuro.net (JK)

Prev by Date: [ale] Cable Modems
Next by Date: [ale] tinyurl down?
Previous by thread: [ale] How to debug a program that just goes away
Next by thread: [ale] How to debug a program that just goes away
Index(es):
- Date
- Thread