From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb@sources.redhat.com, kristian.otnes@tevero.no
Subject: Re: GDB/ELF/Cygwin source path problem
Date: Wed, 24 Sep 2003 12:11:00 -0000 [thread overview]
Message-ID: <200309241211.h8OCB8IG010503@duracef.shout.net> (raw)
Try "gcc -S ...", with all the options that you normally use,
and adding a "-S". Then look in the generated assembly code
and see what the file names look like. That might help.
Try doing the exact "gcc -S ..." with the old working cygwin dll
and the new non-working cygwin dll. Perhaps cygwin.dll changed
in such a way that gcc emits new information now.
Try running the exact same executable with the old and new
cygwin dll. That is, not re-compiling, and with the *exact*
same file.
These things would help localize the problem.
Apologies if this is too simple and you have already done it.
Michael C
GDB QA Guy
next reply other threads:[~2003-09-24 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 12:11 Michael Elizabeth Chastain [this message]
2003-09-24 19:03 ` Kristian Otnes
-- strict thread matches above, loose matches on Subject: below --
2003-09-24 20:09 Michael Elizabeth Chastain
2003-09-24 6:05 Kristian Otnes
2003-09-27 18:58 ` Miki Tebeka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200309241211.h8OCB8IG010503@duracef.shout.net \
--to=mec@shout.net \
--cc=gdb@sources.redhat.com \
--cc=kristian.otnes@tevero.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox