Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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 20:09:00 -0000	[thread overview]
Message-ID: <200309242009.h8OK9Op3016928@duracef.shout.net> (raw)

Hi Kris,

Try coff_symfile_read in coffread.c or elf_symfile_read in elfread.c.
I thought Cygwin was still a COFF platform but if you say it's ELF,
then elfread.c would read it.

> The thing was that the same ELF file gave different results
> with Cygwin version 1.3.22-1 compared to the current
> 1.5.x-y versions available.

Okay, that mostly rules out the idea that gcc is putting strange
information into the file.

> Anyway, what I wanted was to do some old fashioned debugging
> with rebuilding Insight (and GDB) with some printf's inside to
> see what was going on inside the symbol reader. And if anyone
> knows whereabouts source file names and their paths are read,
> I would appreciate a tip.

It's not that hard to debug gdb with gdb.  The procedure is:

  % gdb gdb
  (gdb) set prompt [top] 
  [top] set arge myfile.exe
  [top] break elf_symfile_read
  [top] run

I've never done it with insight so I don't know how the gui plays
with this.

Michael C


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 20:09 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-24 12:11 Michael Elizabeth Chastain
2003-09-24 19:03 ` Kristian Otnes
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=200309242009.h8OK9Op3016928@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