Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Christophe LYON <christophe.lyon@st.com>
Cc: gdb@sourceware.org
Subject: Re: gdb.cp/templates.exp, ctor/dtor breakpoints, etc....
Date: Fri, 16 Jan 2009 15:04:00 -0000	[thread overview]
Message-ID: <20090116150357.GA14717@caradoc.them.org> (raw)
In-Reply-To: <49705F42.5080609@st.com>

On Fri, Jan 16, 2009 at 11:19:46AM +0100, Christophe LYON wrote:
> Hello,
>
> While trying to improve my Open64/Gcc-3-3-3 based compiler results on the 
> gdb-6.8 testsuite, I noticed on gdb.cp/templates.exp that even on  
> x86/GCC-4.1.x there are still several KFAIL tests dating back to 2003.
>
> In particular, there are issues when setting breakpoints on ctor/dtor.
>
> I thought that the recent support for multiple breakpoints would fix  
> this, so I am a bit surprised.

They've all got PRs associated with them that explain the problems.
Most of them seem to deal with menus or with the names of the
constructors/destructors; we've mostly fixed breakpoints by line
number.

> Could someone give me some updated status in this area: should the tests  
> be revisited, or is it GDB itself that should be fixed, or GCC?

In general we use kfail only for GDB bugs, not GCC bugs.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-01-16 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 10:20 Christophe LYON
2009-01-16 15:04 ` Daniel Jacobowitz [this message]
2009-01-16 17:12   ` Christophe LYON
2009-01-16 17:19     ` Daniel Jacobowitz
2009-01-19 15:31       ` Christophe LYON
2009-01-19 15:56         ` 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=20090116150357.GA14717@caradoc.them.org \
    --to=drow@false.org \
    --cc=christophe.lyon@st.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