Re: Stackdump trace - problem and patch

2005-01-02 Thread Christopher Faylor
On Sun, Jan 02, 2005 at 01:55:03PM -0500, Jon A. Lambert wrote: >Christopher Faylor wrote: >>On Sat, Jan 01, 2005 at 03:54:23AM -0500, Jon A. Lambert wrote: >>>my application. I tried various means of examining and setting the >>>registers in the stack to get to a frame that was within my app. I

Re: Stackdump trace - problem and patch

2005-01-02 Thread Jon A. Lambert
Christopher Faylor wrote: On Sat, Jan 01, 2005 at 03:54:23AM -0500, Jon A. Lambert wrote: my application. I tried various means of examining and setting the registers in the stack to get to a frame that was within my app. I have read the various messages on the list describing how to get to those

Re: Stackdump trace - problem and patch

2005-01-01 Thread Christopher Faylor
On Sat, Jan 01, 2005 at 03:54:23AM -0500, Jon A. Lambert wrote: >I was having this difficulty debugging a crashed application. I was using >Cygwin environmental variable error_start to either call dumper or gdb. >Both a core dump and invoking gdb didn't show anything relevant to >my application.

Re: Stackdump trace - problem and patch

2005-01-01 Thread Jon A. Lambert
From: "Jon A. Lambert" <[EMAIL PROTECTED]> --- environ.cc.orig 2005-01-01 03:15:33.913185600 -0500 +++ environ.cc 2005-01-01 03:16:55.670747200 -0500 + int tracesize = strtol (buf, NULL, 0); Sorry I diffed in the wrong dir, that should be.. tracesize = strtol (buf, NULL, 0); -- Unsubscribe info:

Stackdump trace - problem and patch

2005-01-01 Thread Jon A. Lambert
I was having this difficulty debugging a crashed application. I was using Cygwin environmental variable error_start to either call dumper or gdb. Both a core dump and invoking gdb didn't show anything relevant to my application. I tried various means of examining and setting the registers in the