Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Daedalus <daedalus@projecticarus.com>
Cc: gdb@sources.redhat.com
Subject: Re: Is Single step into C++ virtual thunk still broken?
Date: Tue, 09 Jul 2002 11:51:00 -0000	[thread overview]
Message-ID: <20020709185135.GA22053@nevyn.them.org> (raw)
In-Reply-To: <1026240215.1532.14.camel@mojo>

On Tue, Jul 09, 2002 at 07:43:34PM +0100, Daedalus wrote:
> On Tue, 2002-07-09 at 17:27, Daniel Jacobowitz wrote:
> > 
> > Right now, with your test case, I step into the virtual function's
> > thunk - end up at a random line - step again, and end up at the
> > beginning of the virtual function.  Which is annoying but not so bad. 
> > The line I end up at is the first line of the Derived class, which
> > isn't an entirely unreasonable place for the thunk to be but is still
> > probably wrong.  That is a minor GCC bug.
> > 
> > On the other hand, GDB should skip the thunk and step you right into
> > the function being called.  I'll try to think of a way to do this.
> > 
> 
> If, as you suggest, a second step (s command) would take me into the
> virtual function, I could live with the (minor) problem, but here the
> first step command takes me to the closing } of the virtual function
> (although if this is random as you suggest, it might not be significant)
> and the second step (s) command takes me to the next statement after the
> virtual function call, jumping it completely. Very inconvenient.
> 
> In order for me to try and replicate your behaviour, could you give me
> some details?
> 
> I am running the very latest GNU gdb 2002-07-09-cvs, gcc 3.1 and I
> compiled the example with
> 	gcc -g3 -lstdc++ thunk.cpp
> 
> Red Hat Linux 7.3

With 3.0:

drow@nevyn:~/debugging/thunks% gcc-3.0 -g3 -lstdc++ -o vthunk vthunk.cc
drow@nevyn:~/debugging/thunks% gdb ./vthunk                            
GNU gdb 2002-04-01-cvs
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-linux"...
(gdb) b 53
Breakpoint 1 at 0x8048719: file vthunk.cc, line 53.
(gdb) r
Starting program: /home/drow/debugging/thunks/vthunk 

Breakpoint 1, main (argc=1, argv=0xbffff664) at vthunk.cc:53
53              p->VirtualFn();
(gdb) s
virtual thunk to Derived::VirtualFn() (this=0xbffff5e0) at vthunk.cc:23
23      {
(gdb) 
Derived::VirtualFn() (this=0x4001413c) at vthunk.cc:39
39              int a=1;
(gdb) 


With 3.1, same thing.  Curiously, with 2.95 we step right over it...  I
don't have time to investigate why at the moment.

(By the way, you really should use g++ to compile C++ code.)

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-07-09 18:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09  8:56 Daedalus
2002-07-09  9:27 ` Daniel Jacobowitz
2002-07-09 11:44   ` Daedalus
2002-07-09 11:51     ` Daniel Jacobowitz [this message]
2002-07-09 13:10       ` Daedalus
     [not found]         ` <20020709202005.GA23405@nevyn.them.org>
2002-07-09 16:13           ` Daedalus
  -- strict thread matches above, loose matches on Subject: below --
2002-07-09 14:14 Daedalus
2002-07-08  6:47 Daedalus
2002-07-08  6:52 ` Daniel Jacobowitz

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=20020709185135.GA22053@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=daedalus@projecticarus.com \
    --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