This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
RE: c++/1069: Issues printing derived objects with gdb
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 3 Mar 2003 19:58:00 -0000
- Subject: RE: c++/1069: Issues printing derived objects with gdb
- Reply-to: Daniel Jacobowitz <drow at mvista dot com>
The following reply was made to PR c++/1069; it has been noted by GNATS.
From: Daniel Jacobowitz <drow at mvista dot com>
To: gdb-gnats at sources dot redhat dot com
Cc:
Subject: RE: c++/1069: Issues printing derived objects with gdb
Date: Mon, 3 Mar 2003 14:57:40 -0500
The attachment is foo-ver2.tar in GNATS.
----- Forwarded message from Monte Becker <monte at juniper dot net> -----
Date: Fri, 21 Feb 2003 09:11:37 -0500
From: "Monte Becker" <monte at juniper dot net>
Subject: RE: c++/1069: Issues printing derived objects with gdb
To: "Daniel Jacobowitz" <drow at mvista dot com>
Daniel,
Good news! I was able to reproduce the "Execution continues when print value" bug. I simply added threads to the mix.
Attached is a test case including the original test case (named with the original name main.C) and the new one (slightly more original name of mainPThread.C). Build directions are included at the top of the examples. I've also included the resulting a.out file in case that is useful.
I reproduced this bug using the GNU gdb 2003-02-19-cvs version. To see the problem:
1) run program in debugger.
2) set a break in function (with original name) aThread.
3) step past where a is defined.
4) optionally disable breakpoint 1 set in step 2)
5) "p a.gen()" and watch the program continue to completion.
Note also that you don't even get the value of a.gen()
printed out!
Monte
----- End forwarded message -----
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer