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

Daniel Jacobowitz wrote:
> 
> On Sun, Jun 20, 2004 at 09:24:48PM +0200, Otto Wyss wrote:
> > Since a few days GDB (6.1-debian) offsets the shown line by about 3
> > lines. when I set a breakpoint at a function name of a class (C++) it
> > stops and shows the line 3 more down. When I now step through (next)
> 
> Not a known problem - test case?
> 
My full source is here
"http://cvs.sourceforge.net/viewcvs.py/wyodesktop/wyoDesktop/loginapp/src/app.cpp?view=markup"
but it's probably not usable as a test case. The 3 line offset is from
the first function call "App::OnInit".

> Usually this means you've confused GDB about what version of a source
> file it should be opening.
> 
It's definitely not my source since I've built my app and all the
wxWidgets library again. Also I just tried another of my apps (with lots
of wxWidgets functions) and this behaves correctly. Well that means GDB
works correct except in one case.

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?

O. Wyss

-- 
See a huge pile of work at "http://wyodesktop.sourceforge.net/"


  reply	other threads:[~2004-06-21 17:56 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 [this message]
2004-06-21 17:59     ` Daniel Jacobowitz
2004-06-21 18:15       ` Otto Wyss
2004-06-21 19:41         ` Daniel Jacobowitz
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=40D7212F.E68A9D61@orpatec.ch \
    --to=otto.wyss@orpatec.ch \
    --cc=drow@false.org \
    --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