Mail Archives: cygwin/2001/09/21/15:44:27
Kris Erickson wrote:
> I found an old cygwin1.dll (1.3.2(0.39/3/2)) I had backed up earlier
> which works.
> I also tried duplicating the error on a couple of boxes around my work and
> it seems to not be a problem on anyone elses machine (either 2000 ot
> NT). But
> now that I know the problem is in the cygwin1.dll and not gdb or anything else
> I will take a shot at trying to find the problem. Thanks for the pointers
> on how to debug the cygwin1.dll, I hadn't seen that before (perhaps a comment
> in the FAQ saying there are extra how-to's in the
> src/cygwin-xxx/winsup/cygwin dir)
>
I have had the same problem with cygwin 1.3.3-2 under Win2K. I have installed
cygwin 1.3.2-1
and there are no more problems with gdb. So I can confirm this statement.
Ralf
> Thanks again your help...
>
> Kris
>
> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com]
> Sent: Thursday, September 20, 2001 2:07 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: Help... GDB no longer works after updating...
>
>
> On Thu, Sep 20, 2001 at 02:42:11PM -0600, Mark Paulus wrote:
> >If you are having problems, and you can't debug gdb, then try this:
> >
> >Recompile/relink gdb with a -Wl,-Map -Wl,gdb.map option. Then when you
> >get your crash message, you should be able to go back to the map file,
> >and figure out which subroutine/code segment is causing the problem.
> >Then you might be able to either desk check the code slightly, or rerun
> >gdb on gdb, and dissassemble the subroutine in question. This should
> >allow you to get to the exact machine instruction, which will take you
> >back to the high level code involved, and then it's a matter of
> >figuring out which variable is whacked, or when/how the stack is
> >overflowing and whacking the code segment, etc, etc.
>
> You might also be able to use the techniques here:
> http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/how-to-
debug-cygwin.txt?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=src
to debug the application. This would require using an older
cygwin1.dll that works, assuming that cygwin1.dll is the
problem.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -