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

On Tue, 2002-07-09 at 19:51, Daniel Jacobowitz wrote:
> 
> 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.)
> 

Compared with my experience ( Using g++ ;) )

[daedalus@mojo thunk]$ g++ --version
g++ (GCC) 3.1
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.

[daedalus@mojo thunk]$ g++ -g3 -lstdc++ -o thunk thunk.cpp
[daedalus@mojo thunk]$ gdb ./thunk
GNU gdb 2002-07-09-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 "i686-pc-linux-gnu"...
(gdb) b 50
Breakpoint 1 at 0x80486ce: file thunk.cpp, line 50.
(gdb) r
Starting program: /home/daedalus/src/thunk/thunk 

Breakpoint 1, main (argc=1, argv=0xbffff9f4) at thunk.cpp:50
50		p->VirtualFn();
(gdb) s
virtual thunk to Derived::VirtualFn() () at thunk.cpp:43
43	}
(gdb) s
main (argc=1, argv=0xbffff9f4) at thunk.cpp:51
51		return 0;
(gdb) 


Ho hum. Thanks for your input anyway.

Andrew Walrond
Project Icarus


  reply	other threads:[~2002-07-09 20:10 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
2002-07-09 13:10       ` Daedalus [this message]
     [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=1026245359.1532.22.camel@mojo \
    --to=daedalus@projecticarus.com \
    --cc=drow@mvista.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