Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Roland Schwingel <roland.schwingel@onevision.de>
To: Kai.tietz@onevision.com, gdb <gdb@sourceware.org>
Subject: Re: gdb_assert when resetting breakpoints
Date: Tue, 17 Mar 2009 11:44:00 -0000	[thread overview]
Message-ID: <49BF8D2D.1020605@onevision.de> (raw)

Hi Kai,

Kai Tietz wrote on 17.03.2009 11:24:25:
 > Roland Schwingel wrote on 10.03.2009 15:02:40:
 >
 > > Hi...
 > >
 > > When using current gdb cvs head sources I encounter a gdb_assert() in
 > > breakpoint.c line 7451.
 > > This is in function breakpoint_re_set_one().
 > >
 > > ...
 > >
 > > Thanks in advance for your help,
 > >
 > > Roland
 >
 > Hi,
 >
 > I prepared a patch for this issue, which should solve the described
 > problem of Roland.
 >
 > Changelog:
 >
 > 2009-03-17  Kai Tietz  <Kai.Tietz@onevision.com>
 >
 >         * breakpoint.c: take care about multiple breakpoints
 >         possibilities when resetting breakpoints.
 >
 >
 > Is this patch ok for apply?
 >
 > Cheers,
 > Kai

Thanks for your patch and your work. I just tried it and it works
without trouble and solves the problems in resetting the breakpoints for me.
It looks quite similar to what I did for myself. I couldn't find a 
problem upto
now with your patch. I think it would be could if this could make it to 
gdb's
mainline. Others might also profit from that.

Thank you very much,

Roland



             reply	other threads:[~2009-03-17 11:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 11:44 Roland Schwingel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-10 16:45 Roland Schwingel
2009-03-10 14:02 Roland Schwingel
2009-03-10 15:39 ` Paul Pluzhnikov
2009-03-17 10:24 ` Kai Tietz
2009-03-21 16:26   ` Kai Tietz
2009-04-30 21:37     ` Joel Brobecker

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=49BF8D2D.1020605@onevision.de \
    --to=roland.schwingel@onevision.de \
    --cc=Kai.tietz@onevision.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