Mail Archives: cygwin/2001/09/20/17:07:45
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/
- Raw text -