From: "Miki Tebeka" <mikit@zoran.co.il>
To: <gdb@sources.redhat.com>
Subject: RE: GDB/ELF/Cygwin source path problem
Date: Sat, 27 Sep 2003 18:58:00 -0000 [thread overview]
Message-ID: <HGEOJOCIOKDJGKFDEIBAAEJACDAA.mikit@zoran.co.il> (raw)
In-Reply-To: <3F710C4C@epostleser.online.no>
Hello Kris,
>That worked fine until recent updates in Cygwin (around Sept. 1 2003)
>environment. I now have problems with high level debugging due to that
>the path information in the source files in most cases are missing.
>The problem was introduced by simply updating Cygwin, ie. no changes
>in Insight/GDB.
>
>(Source paths are typically missing if the source file is located
>in the same directory as the compiler is running, something which
>is what our make system usually does. If the source file is located
>in for instance "../" relative to where the compiler is running, the
>source path is seen. I have checked the ELF file, and source paths
>are included for all files.)
>
>This is probably related to the symbol reader in GDB. I think that Cygwin
>has changed somewhat with respect to fstat() contents etc.
Try running gdb without the UI (gdb -nw) and see if the problem continues.
If you're ok without UI then it's a tcl/tk problem and you need to have a
look
at the tcl source (libgui/library ?)
HTH.
Bye.
----------------------------------------------------------------------------
-
Smile, damn it, smile.
lambda msg: {
'name' : 'Miki Tebeka',
'email' : 'mikit@zoran.co.il',
'url' : ' http://www.cs.bgu.ac.il/~tebeka',
'quote' : 'The only difference between children and adults is the
price of the toys'
}[msg]
next prev parent reply other threads:[~2003-09-27 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 6:05 Kristian Otnes
2003-09-27 18:58 ` Miki Tebeka [this message]
2003-09-24 12:11 Michael Elizabeth Chastain
2003-09-24 19:03 ` Kristian Otnes
2003-09-24 20:09 Michael Elizabeth Chastain
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=HGEOJOCIOKDJGKFDEIBAAEJACDAA.mikit@zoran.co.il \
--to=mikit@zoran.co.il \
--cc=gdb@sources.redhat.com \
/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