Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
To: <michaelstather@nuzi.de>
Cc: gdb@sources.redhat.com
Subject: Re: Path handling bug in GDB included with MingW 3.1.0-1
Date: Tue, 07 Oct 2003 21:30:00 -0000	[thread overview]
Message-ID: <1438-Tue07Oct2003231328+0200-eliz@elta.co.il> (raw)
In-Reply-To: <002d01c38b8a$6e2d34f0$2101a8c0@kyromaster> (michaelstather@nuzi.de)

> From: "Michael Stather" <michaelstather@nuzi.de>
> Date: Sun, 5 Oct 2003 23:48:35 +0200
> 
> g++ -g -o p.exe c:/p/p.cpp -mwindows
> gdb
> break "c:/p/p.cpp:7"
> Run
> 
> gdb won\x7ft stop at the breakpoint.
> however if I do:
> 
> cd c:\m
> g++ -g -o p.exe p.cpp -mwindows
> gdb
> break "p.cpp:7"
> run
> 
> it breaks correctly.

Sounds like the MinGW port isn't writing leading directories of the
files into the debug info.

Questions:

What is the default debug info format used by the MinGW port of GCC?

Does it help to use -gstabs+ instead of just -g?

Do you see the leading directories of the source file names if you
run "objdump --debug" on the object files?


  parent reply	other threads:[~2003-10-07 21:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-05 21:48 Michael Stather
2003-10-05 22:48 ` Christopher Faylor
2003-10-07 21:30 ` Eli Zaretskii [this message]
2003-10-07 23:22   ` Christopher Faylor
2003-10-08  5:51     ` Eli Zaretskii
2003-10-08 13:43       ` Christopher Faylor
2003-10-08 18:20         ` Support for unofficial GDB (was: Path handling bug in GDB included with MingW 3.1.0-1) Eli Zaretskii
2003-10-08  0:34   ` Path handling bug in GDB included with MingW 3.1.0-1 Chris Johns
2003-10-08  5:54     ` Eli Zaretskii

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=1438-Tue07Oct2003231328+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=michaelstather@nuzi.de \
    /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