From: Frederic Riss <frederic.riss@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [patch 1/3] Clear stale specific locs, not whole bpts [rediff]
Date: Thu, 10 Jun 2010 14:09:00 -0000 [thread overview]
Message-ID: <AANLkTikNQTVvNDKs8JXZX89la7Cu6MFoGBMpj_8gjDjb@mail.gmail.com> (raw)
In-Reply-To: <20100607134011.GA10971@host0.dyn.jankratochvil.net>
Hi !
On 7 June 2010 15:40, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> Checked-in:
> http://sourceware.org/ml/gdb-cvs/2010-06/msg00058.html
Seems that this commit is partially broken. In non-stop mode, after
deleteing a step breakpoint, GDB call print_it_typical () on a bpstat
that references that moribund breakpoint. Looking at the
print_it_typical () code, you'll quickly see that this means crash.
It's very easy to reproduce:
------ foo.c ---------------------------
int foo () {
return 0;
}
int main (int argc, char *argv[])
{
return foo ();
}
------ foo.c ---------------------------
gcc -g foo.c && gdb a.out -ex 'set non-stop' -ex start -ex n
Cheers,
Fred
next prev parent reply other threads:[~2010-06-10 14:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 20:02 [patch 1/3] Clear stale specific locs, not whole bpts Jan Kratochvil
2010-05-17 21:25 ` [patch 1/3] Clear stale specific locs, not whole bpts [rediff] Jan Kratochvil
2010-05-24 12:18 ` Pedro Alves
2010-06-04 19:19 ` Jan Kratochvil
2010-06-07 11:50 ` Pedro Alves
2010-06-07 13:40 ` Jan Kratochvil
2010-06-10 14:09 ` Frederic Riss [this message]
2010-06-10 20:39 ` Jan Kratochvil
2010-06-11 7:58 ` Frederic Riss
2010-06-11 13:00 ` Jan Kratochvil
2010-06-11 10:50 ` Pedro Alves
2010-06-11 16:24 ` Ulrich Weigand
2010-06-11 18:34 ` Jan Kratochvil
2010-06-11 21:51 ` Ulrich Weigand
2010-06-11 21:59 ` Jan Kratochvil
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=AANLkTikNQTVvNDKs8JXZX89la7Cu6MFoGBMpj_8gjDjb@mail.gmail.com \
--to=frederic.riss@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pedro@codesourcery.com \
/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