From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix double free on error while inserting the breakpoint
Date: Wed, 22 Apr 2009 23:11:00 -0000 [thread overview]
Message-ID: <m3eivkthb6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20081122214006.GA22076@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Sat\, 22 Nov 2008 22\:40\:06 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> x86 requires to build GDB with -lmcheck to make the crash reproducible.
FWIW, I reproduced this with valgrind.
Jan> 2008-11-22 Jan Kratochvil <jan.kratochvil@redhat.com>
Jan> Fix double free on error inserting the breakpoint instruction.
Jan> * breakpoint.c (create_breakpoints): Move the
Jan> update_global_location_list call to ...
Jan> (break_command_really): ... here together with the second local call
Jan> both unified after all the cleanups.
I like this but I am unsure whether it is ok to move the call to
update_global_location_list past the call to mention.
Jan> + /* Have already BREAKPOINT_CHAIN discarded as we may get an exception while
Jan> + inserting the breakpoints which would double-free the resources both by
Jan> + BREAKPOINT_CHAIN now and during DELETE_BREAKPOINT in the future. */
Jan> + update_global_location_list (1);
I found this comment pretty hard to follow. I think the code would be
pretty clear without it.
Tom
next prev parent reply other threads:[~2009-04-22 23:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 3:35 Jan Kratochvil
2009-04-22 23:11 ` Tom Tromey [this message]
2009-04-23 20:36 ` Jan Kratochvil
2009-04-23 21:25 ` Tom Tromey
2009-04-23 22:40 ` 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=m3eivkthb6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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