Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Otto Wyss <otto.wyss@orpatec.ch>
Cc: gdb@sources.redhat.com
Subject: Re: GDB doesn't show the correct line
Date: Mon, 21 Jun 2004 19:41:00 -0000	[thread overview]
Message-ID: <20040621194138.GA19693@nevyn.them.org> (raw)
In-Reply-To: <40D725AF.FC2AAF3A@orpatec.ch>

On Mon, Jun 21, 2004 at 08:15:10PM +0200, Otto Wyss wrote:
> Daniel Jacobowitz wrote:
> > 
> > > I can only speculate that it's because of one of the standard headers
> > > which are unique to this program. But they are from an ordinary
> > > Debian/sarge system. How can I detect further where the offset is introduced?
> > 
> > The only things that I can recommend:
> >   - Look at the preprocessor output (gcc -E).  See if there are missing
> >     #line directives (usually just "# <num>" in preprocessor output).
> >     The syntax of these things is really hard to read.
> >   - Look at the debug info with readelf -wl and compare it to the
> >     object code.
> > 
> Not a very nice prospect, I guess I won't be able to detect anything
> useful within resonable time :-(
> 
> > It sounds like it is more likely to be a problem with GCC's output than
> > GDB's parsing.
> > 
> I just inserted a syntax error in my source, at least GCC reports the
> correct line number.
> 
> Can't this line number problem somehow detected within GDB? Sorry if I
> ask this as someone without knowing any internals but IMO this would be
> the best solution. My app is now working so I'm not in a hurry but a
> good debugger is _essential_  for any development.

Not without knowing what the problem _is_ - which we don't until
someone does the analysis I described above.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-06-21 19:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-20 19:24 Otto Wyss
2004-06-20 20:29 ` Daniel Jacobowitz
2004-06-21 17:56   ` Otto Wyss
2004-06-21 17:59     ` Daniel Jacobowitz
2004-06-21 18:15       ` Otto Wyss
2004-06-21 19:41         ` Daniel Jacobowitz [this message]
2004-11-13 20:50         ` Daniel Jacobowitz
2004-11-13 20:55           ` Otto Wyss
2004-11-13 21:43             ` Daniel Jacobowitz
2004-11-14  4:36               ` Otto Wyss
2004-11-13 21:46           ` Eli Zaretskii
2004-11-13 21:59             ` Daniel Jacobowitz
2004-11-14  5:30               ` Eli Zaretskii
2004-11-14 14:38               ` Tom Tromey
2004-11-14 21:43                 ` Eli Zaretskii
2004-11-14 22:29                   ` Andreas Schwab
2004-11-14 22:39                     ` Eli Zaretskii
2004-11-15  4:41                       ` Andreas Schwab
2004-11-15 16:06                         ` Eli Zaretskii
2004-11-14 23:37                   ` Felix Lee
2004-11-15  4:45                     ` Eli Zaretskii
2004-06-23 11:54   ` Tarjei Knapstad

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=20040621194138.GA19693@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=otto.wyss@orpatec.ch \
    /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