public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Brian Budge <brian.budge@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: can't step into, or print variables inside of C++ template function
Date: Fri, 29 Apr 2011 13:15:00 -0000	[thread overview]
Message-ID: <20110429131446.GA25816@host1.jankratochvil.net> (raw)
In-Reply-To: <BANLkTi=rr_BL1S=jYjMB3qhwuG988txuuA@mail.gmail.com>

On Wed, 27 Apr 2011 18:43:16 +0200, Brian Budge wrote:
> A quick update:  This works under gcc 4.4.  Unsure if a bug should be
> filed against gdb to work with newer debug information, or against gcc
> for breaking the debug information.

Sometimes it is GCC bug, sometimes GDB bug.  But the GCC or GDB maintainers
will reassign it appropriately when needed.

It is more important to file a reproducer, I cannot say anything more about
it.  Both GCC and GDB have heavy regression testsuites and apparently this
case is not yet covered there.


Thanks,
Jan

      reply	other threads:[~2011-04-29 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 16:41 Brian Budge
2011-04-27 16:43 ` Brian Budge
2011-04-29 13:15   ` Jan Kratochvil [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=20110429131446.GA25816@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brian.budge@gmail.com \
    --cc=gdb@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).