From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: RFC: don't set the pspace on ordinary breakpoints
Date: Thu, 10 Nov 2011 16:53:00 -0000 [thread overview]
Message-ID: <m3d3czdind.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m362itf8b9.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed, 09 Nov 2011 11:40:42 -0700")
Pedro> Any chance we can have a standalone patch for just the
Pedro> startup-disabled changes? We'd need something like my previous
Pedro> suggestion in bkpt_re_set (even if we'd remain buggy WRT
Pedro> multi-process).
Tom> Sure, I will do that.
Here it is.
Built and regtested on x86-64 F15.
Tom
2011-10-28 Tom Tromey <tromey@redhat.com>
* breakpoint.h (enum enable_state) <bp_startup_disabled>: Remove.
* breakpoint.c (should_be_inserted): Explicitly check if program
space is executing startup.
(describe_other_breakpoints): Update.
(disable_breakpoints_before_startup): Change executing_startup
earlier. Use location's pspace.
(enable_breakpoints_after_startup): Likewise.
(init_breakpoint_sal): Don't use bp_startup_disabled.
(create_breakpoint): Don't use bp_startup_disabled.
(update_global_location_list): Use should_be_inserted.
(bkpt_re_set): Update.
From c8c42dffe736323958542623c1ca5e61db923a95 Mon Sep 17 00:00:00 2001
From: Tom Tromey <tromey@redhat.com>
Date: Thu, 10 Nov 2011 08:55:34 -0700
Subject: [PATCH 1/3] remove bp_startup_disabled
---
gdb/ChangeLog | 14 ++++++++++++
gdb/breakpoint.c | 61 +++++++++++++++++++++--------------------------------
gdb/breakpoint.h | 8 -------
3 files changed, 38 insertions(+), 45 deletions(-)
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 8c98bef..ec45335 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -1568,6 +1568,9 @@ should_be_inserted (struct bp_location *bl)
if (!bl->enabled || bl->shlib_disabled || bl->duplicate)
return 0;
+ if (user_breakpoint_p (bl->owner) && bl->pspace->executing_startup)
+ return 0;
+
/* This is set for example, when we're attached to the parent of a
vfork, and have detached from the child. The child is running
free, and we expect it to do an exec or exit, at which point the
@@ -5313,8 +5316,7 @@ describe_other_breakpoints (struct gdbarch *gdbarch,
printf_filtered (" (thread %d)", b->thread);
printf_filtered ("%s%s ",
((b->enable_state == bp_disabled
- || b->enable_state == bp_call_disabled
- || b->enable_state == bp_startup_disabled)
+ || b->enable_state == bp_call_disabled)
? " (disabled)"
: b->enable_state == bp_permanent
? " (permanent)"
@@ -6933,48 +6935,48 @@ enable_watchpoints_after_interactive_call_stop (void)
void
disable_breakpoints_before_startup (void)
{
- struct breakpoint *b;
+ struct bp_location *loc, **locp_tmp;
int found = 0;
- ALL_BREAKPOINTS (b)
+ current_program_space->executing_startup = 1;
+
+ ALL_BP_LOCATIONS (loc, locp_tmp)
{
- if (b->pspace != current_program_space)
+ if (loc->pspace != current_program_space)
continue;
- if ((b->type == bp_breakpoint
- || b->type == bp_hardware_breakpoint)
- && breakpoint_enabled (b))
+ if ((loc->owner->type == bp_breakpoint
+ || loc->owner->type == bp_hardware_breakpoint)
+ && breakpoint_enabled (loc->owner))
{
- b->enable_state = bp_startup_disabled;
found = 1;
+ break;
}
}
if (found)
update_global_location_list (0);
-
- current_program_space->executing_startup = 1;
}
void
enable_breakpoints_after_startup (void)
{
- struct breakpoint *b;
+ struct bp_location *loc, **locp_tmp;
int found = 0;
current_program_space->executing_startup = 0;
- ALL_BREAKPOINTS (b)
+ ALL_BP_LOCATIONS (loc, locp_tmp)
{
- if (b->pspace != current_program_space)
+ if (loc->pspace != current_program_space)
continue;
- if ((b->type == bp_breakpoint
- || b->type == bp_hardware_breakpoint)
- && b->enable_state == bp_startup_disabled)
+ if ((loc->owner->type == bp_breakpoint
+ || loc->owner->type == bp_hardware_breakpoint)
+ && breakpoint_enabled (loc->owner))
{
- b->enable_state = bp_enabled;
found = 1;
+ break;
}
}
@@ -7256,11 +7258,6 @@ init_breakpoint_sal (struct breakpoint *b, struct gdbarch *gdbarch,
"tracepoint marker to probe"));
}
- if (enabled && b->pspace->executing_startup
- && (b->type == bp_breakpoint
- || b->type == bp_hardware_breakpoint))
- b->enable_state = bp_startup_disabled;
-
loc = b->loc;
}
else
@@ -7983,11 +7980,6 @@ create_breakpoint (struct gdbarch *gdbarch,
b->pspace = current_program_space;
b->py_bp_object = NULL;
- if (enabled && b->pspace->executing_startup
- && (b->type == bp_breakpoint
- || b->type == bp_hardware_breakpoint))
- b->enable_state = bp_startup_disabled;
-
if (!internal)
/* Do not mention breakpoints with a negative number,
but do notify observers. */
@@ -10607,13 +10599,8 @@ update_global_location_list (int should_insert)
struct breakpoint *b = loc->owner;
struct bp_location **loc_first_p;
- if (b->enable_state == bp_disabled
- || b->enable_state == bp_call_disabled
- || b->enable_state == bp_startup_disabled
- || !loc->enabled
- || loc->shlib_disabled
- || !breakpoint_address_is_meaningful (b)
- || is_tracepoint (b))
+ if (!should_be_inserted (loc)
+ || !breakpoint_address_is_meaningful (b))
continue;
/* Permanent breakpoint should always be inserted. */
@@ -10891,8 +10878,7 @@ static struct breakpoint_ops base_breakpoint_ops =
static void
bkpt_re_set (struct breakpoint *b)
{
- /* Do not attempt to re-set breakpoints disabled during startup. */
- if (b->enable_state == bp_startup_disabled)
+ if (current_program_space->executing_startup)
return;
/* FIXME: is this still reachable? */
@@ -11825,6 +11811,7 @@ addr_string_to_sals (struct breakpoint *b, char *addr_string, int *found)
if (e.error == NOT_FOUND_ERROR
&& (b->condition_not_parsed
|| (b->loc && b->loc->shlib_disabled)
+ || (b->loc && b->loc->pspace->executing_startup)
|| b->enable_state == bp_disabled))
not_found_and_ok = 1;
diff --git a/gdb/breakpoint.h b/gdb/breakpoint.h
index fe381df..d9060cf 100644
--- a/gdb/breakpoint.h
+++ b/gdb/breakpoint.h
@@ -186,14 +186,6 @@ enum enable_state
automatically enabled and reset when the
call "lands" (either completes, or stops
at another eventpoint). */
- bp_startup_disabled, /* The eventpoint has been disabled during
- inferior startup. This is necessary on
- some targets where the main executable
- will get relocated during startup, making
- breakpoint addresses invalid. The
- eventpoint will be automatically enabled
- and reset once inferior startup is
- complete. */
bp_permanent /* There is a breakpoint instruction
hard-wired into the target's code. Don't
try to write another breakpoint
--
1.7.6.4
next prev parent reply other threads:[~2011-11-10 16:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 15:32 Tom Tromey
2011-10-31 1:03 ` Jan Kratochvil
2011-10-31 12:07 ` Yao Qi
2011-11-02 18:55 ` Pedro Alves
2011-11-02 19:47 ` Tom Tromey
2011-11-02 20:21 ` Pedro Alves
2011-11-03 14:01 ` Tom Tromey
2011-11-03 16:02 ` Pedro Alves
2011-11-03 19:33 ` Ulrich Weigand
2011-11-08 19:32 ` Tom Tromey
2011-11-08 20:23 ` Tom Tromey
2011-11-09 18:24 ` Tom Tromey
2011-11-09 18:30 ` Pedro Alves
2011-11-09 18:41 ` Tom Tromey
2011-11-10 16:53 ` Tom Tromey [this message]
2011-11-10 17:49 ` Pedro Alves
2011-11-10 17:57 ` Ulrich Weigand
2011-11-10 19:27 ` Tom Tromey
2011-11-10 20:23 ` Tom Tromey
2011-11-11 12:56 ` Ulrich Weigand
2011-11-11 14:47 ` Tom Tromey
2011-11-14 21:12 ` Tom Tromey
2011-11-16 18:37 ` Ulrich Weigand
2011-11-16 21:24 ` Tom Tromey
2011-11-18 18:31 ` Ulrich Weigand
2012-01-02 18:18 ` [7.4 regression] Stand-alone Cell debugging broken (Re: RFC: don't set the pspace on ordinary breakpoints) Ulrich Weigand
2012-01-03 3:15 ` Joel Brobecker
2012-01-03 20:29 ` Tom Tromey
2012-01-04 12:36 ` Ulrich Weigand
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=m3d3czdind.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=uweigand@de.ibm.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