Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kristian Otnes <kristian.otnes@tevero.no>
To: gdb@sources.redhat.com
Subject: GDB/ELF/Cygwin source path problem
Date: Wed, 24 Sep 2003 06:05:00 -0000	[thread overview]
Message-ID: <3F710C4C@epostleser.online.no> (raw)

I have been using Insight (with GDB embedded) for a cross target
PowerPC-ELF configuration.

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.

Could anyone please inform me where to look in the GDB source files
for adding some debug printout in order to fix the problem? I
started looking into it, but got lost somewhere in there trying
to grasp all the internal structures.

Best regards
Kris.


             reply	other threads:[~2003-09-24  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24  6:05 Kristian Otnes [this message]
2003-09-27 18:58 ` Miki Tebeka
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=3F710C4C@epostleser.online.no \
    --to=kristian.otnes@tevero.no \
    --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