[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: jknapka at kneuro.net (JK)
Date: Fri, 26 Feb 2010 09:27:42 -0700
In-reply-to: <[email protected]>
References: <[email protected]> <1267190530.14961.95.camel@cfowler-desktop> <[email protected]> <[email protected]> <[email protected]>

On 2/26/2010 9:26 AM, JK wrote:
> Shouldv'e read the OP more closely before replying. You're
> already doing most of this. I'd first recompile with
> optimization turned off and see if the problem persists.


BTW: Your code and all dependencies, preferably.

-- JK


-- 
We Americans are a freedom-loving people, and nothing says "freedom"
like Getting Away With It. -- Guy Forsyth, "Long Long Time"

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)
- [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] Cable Modems
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