public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/12266] Typedefs are not expanded to their base types in breakpoint definitions
Date: Thu, 17 Mar 2011 18:07:00 -0000	[thread overview]
Message-ID: <bug-12266-4717-gcSorKOqg3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12266-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12266

--- Comment #5 from Keith Seitz <keiths at redhat dot com> 2011-03-17 18:07:41 UTC ---
Since I have committed the patchset for 11734 and 12273, I am now revisiting
this bug...

There /appear/ to be multiple problems with symbol lookup that cause this
failure.  I have further reduced the test case to:

#include <stdlib.h>

typedef const char* const* my_type;
typedef my_type my_other_type;

void
test (my_other_type foo) { }

int
main (void)
{
  test (NULL);
  return 0;
}


Breaking on "test(my_other_type)" works, but breaking on either "test(my_type)"
or "test(const char* const*)" does not.  This partly occurs because
dwarf2_physname calls c_type_print_args, and that function does not do any
typedef resolution (which it should when it is used to compute physnames). 
Unfortunately, fixing that still doesn't work right, either.

But I just wanted to update this bug to let anyone watching it know that I am
taking a look at it.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-03-17 18:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 20:47 [Bug c++/12266] New: " anonyme_uprh at hotmail dot com
2010-12-07 21:19 ` [Bug c++/12266] " keiths at redhat dot com
2011-01-31 13:10 ` anonyme_uprh at hotmail dot com
2011-02-17 21:09 ` keiths at redhat dot com
2011-02-18 10:25 ` anonyme_uprh at hotmail dot com
2011-02-18 10:27 ` anonyme_uprh at hotmail dot com
2011-03-17 18:07 ` keiths at redhat dot com [this message]
2011-03-23 17:49 ` anonyme_uprh at hotmail dot com
2011-03-30 15:08 ` keiths at redhat dot com
2011-08-01 20:22 ` keiths at redhat dot com
2011-08-02 17:17 ` anonyme_uprh at hotmail dot com
2011-08-02 17:24 ` keiths at redhat dot com
2011-08-18 21:45 ` cvs-commit at gcc dot gnu.org
2011-08-18 22:19 ` anonyme_uprh at hotmail dot com
2011-08-19 10:01 ` keiths at redhat dot com

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=bug-12266-4717-gcSorKOqg3@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).