From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Vladimir Prus <vladimir@codesourcery.com>
Subject: Re: functions that delete breakpoints should not insert bp locations (was: Fix execl.exp sporadic failures)
Date: Mon, 07 Jul 2008 19:06:00 -0000 [thread overview]
Message-ID: <20080707190539.GB11544@caradoc.them.org> (raw)
In-Reply-To: <200807031145.54289.pedro@codesourcery.com>
On Thu, Jul 03, 2008 at 11:45:53AM +0100, Pedro Alves wrote:
> 2008-07-03 Pedro Alves <pedro@codesourcery.com>
>
> * breakpoint.c (update_global_location_list): Add boolean
> "should_insert" argument. Only insert locations if caller told it
> too.
> (update_global_location_list_nothrow): Add boolean "should_insert"
> argument. Pass it to update_global_location_list.
> (insert_breakpoints, create_longjmp_breakpoint)
> (create_overlay_event_breakpoint, enable_overlay_breakpoints)
> (create_thread_event_breakpoint, create_solib_event_breakpoint)
> (create_fork_vfork_event_catchpoint, create_exec_event_catchpoint)
> (enable_watchpoints_after_interactive_call_stop)
> (set_momentary_breakpoint, create_breakpoints)
> (break_command_really, watch_command_1)
> (create_ada_exception_breakpoint, update_breakpoint_locations)
> (do_enable_breakpoint, enable_command): Pass true to
> update_global_location_list.
> (bpstat_stop_status, disable_overlay_breakpoints)
> (disable_watchpoints_before_interactive_call_start)
> (delete_breakpoint, disable_breakpoint, disable_command): Pass
> false to update_global_location_list.
> (update_breakpoints_after_exec): Don't temporarily disable
> always-inserted mode.
Thanks, this is OK.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-07-07 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 1:27 Pedro Alves
2008-07-03 8:48 ` Vladimir Prus
2008-07-03 10:46 ` Pedro Alves
2008-07-07 19:06 ` Daniel Jacobowitz [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=20080707190539.GB11544@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=vladimir@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