Using cygwin1.dbg

2007-03-16 Thread Charles Wilson
I'm attempting to debug an issue with libtool, and it seems to be related to the implementation of argz_insert and/or realloc within newlib/cygwin. I'm using cygwin kernel 1.5.24-2, so I downloaded cygwin-1.5.24-2-src, and copied the cygwin1.dbg file from there into /usr/bin/ When I

Re: Using cygwin1.dbg

2007-03-16 Thread Christopher Faylor
On Fri, Mar 16, 2007 at 11:46:21AM -0500, Charles Wilson wrote: I'm attempting to debug an issue with libtool, and it seems to be related to the implementation of argz_insert and/or realloc within newlib/cygwin. I'm using cygwin kernel 1.5.24-2, so I downloaded cygwin-1.5.24-2-src, and copied

Re: Using cygwin1.dbg

2007-03-16 Thread Charles Wilson
Christopher Faylor wrote: On Fri, Mar 16, 2007 at 11:46:21AM -0500, Charles Wilson wrote: Or should I just build the kernel unstripped using cygwin-1.5.24-2-src, and debug against that? Corinna has been responsible for the last few cygwin 1.5.2x releases and she has a different way of

Re: Using cygwin1.dbg

2007-03-16 Thread Christopher Faylor
On Fri, Mar 16, 2007 at 12:49:10PM -0500, Charles Wilson wrote: Christopher Faylor wrote: On Fri, Mar 16, 2007 at 11:46:21AM -0500, Charles Wilson wrote: Or should I just build the kernel unstripped using cygwin-1.5.24-2-src, and debug against that? Corinna has been responsible for the last few

Re: Using cygwin1.dbg

2007-03-16 Thread Brian Dessent
Charles Wilson wrote: When I launched gdb/insight (gdb-20060706-2) on my target app, and ran the target, I got two popup windows: section .text not found in /usr/bin/cygwin1.dbg no loadable sections found in added symbol-file /usr/bin/cygwin1.dbg This is just a bug in insight. It has

Re: Using cygwin1.dbg

2007-03-16 Thread Charles Wilson
Brian Dessent wrote: This is just a bug in insight. It has existed for some time. There is code in gdb to supress these errors when loading the debug file, but when running under insight the plumbing for messages is different and so they get displayed. I've been meaning to look into this for

Re: Using cygwin1.dbg

2007-03-16 Thread Brian Dessent
Charles Wilson wrote: Err, ok. But shouldn't I be able to do source-level debugging, rather than asm-only? (That is one difference between using cygwin1.dll alone, and with cygwin1.dbg: in the former case, cygwin calls are simply stepped over, even in I try to step into. In the latter