[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: cfowler at outpostsentinel.com (Chris Fowler)
Date: Fri, 26 Feb 2010 11:27:26 -0500
In-reply-to: <[email protected]>
References: <[email protected]> <1267190530.14961.95.camel@cfowler-desktop> <[email protected]> <[email protected]>

On Fri, 2010-02-26 at 09:12 -0700, JK wrote:
> If your program is a memory hog, the Out-Of-Memory
> killer in the kernel's VM subsystem may be the culprit.

http://web.hexapodia.org/~adi/pmap.c

Follow-Ups:
- [ale] How to debug a program that just goes away
  - From: ale_nospam at fayettedigital.com (Jim Lynch)

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] How to debug a program that just goes away
Next by Date: [ale] How to debug a program that just goes away
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