From: "Martin Schröder" <gschroeder@onlinehome.de>
To: <gdb@sourceware.org>
Subject: Re: Breakpoint troubles on typedefs
Date: Thu, 25 Nov 2010 10:29:00 -0000 [thread overview]
Message-ID: <3278F49FBE754FAE8F7A6A2AFCF26DD9@igor> (raw)
In-Reply-To: <E7E3B2A3F11D407299DA8B013461DF5A@igor>
Martin Schröder wrote:
> Tom Tromey wrote:
>>>>>>> "Martin" == Martin Schröder <gschroeder@onlinehome.de> writes:
>>
>>> I seem to have found a bug / feature in GDB 7.2 for C++. The
>>> problem is that typedefs are not converted to their base type
>>> when one tries to set a breakpoint into a function that has a
>>> typedef'd type as Martin> parameter.
>>>
>>> Could you file this in GDB's bugzilla?
>>>
>>> A group of us are actively working on C++-related problems in
>>> GDB. It is best for us if bugs are in bugzilla so we don't miss
>>> any.
>
> Sure, will do so tomorrow (it's past midnight where I hail from).
>
Here's the link to the bugzilla entry:
http://sourceware.org/bugzilla/show_bug.cgi?id=12266
So long,
Martin.
prev parent reply other threads:[~2010-11-25 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 19:47 Martin Schröder
2010-11-23 21:15 ` Tom Tromey
2010-11-24 0:25 ` Martin Schröder
2010-11-25 10:29 ` Martin Schröder [this message]
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=3278F49FBE754FAE8F7A6A2AFCF26DD9@igor \
--to=gschroeder@onlinehome.de \
--cc=gdb@sourceware.org \
--cc=lionhead@onlinehome.de \
/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