Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Share the shared library list between inferiors
Date: Mon, 03 Nov 2008 16:15:00 -0000	[thread overview]
Message-ID: <200811031614.13618.pedro@codesourcery.com> (raw)
In-Reply-To: <20081103151302.GA31147@caradoc.them.org>

[-- Attachment #1: Type: text/plain, Size: 292 bytes --]

On Monday 03 November 2008 15:13:02, Daniel Jacobowitz wrote:

> I think the name is fine - if we need some day to separate these
> features, then we'll create extra gdbarch knobs for them.

Ok then.  I checked this in to mention the feature's impact
on breakpoints.

Thanks,
-- 
Pedro Alves

[-- Attachment #2: mention_global_breakpoints.diff --]
[-- Type: text/x-diff, Size: 1914 bytes --]

2008-11-03  Pedro Alves  <pedro@codesourcery.com>

	* gdbarch.sh (has_global_solist): Mention global breakpoints.
	* gdbarch.h: Regenerate.

---
 gdb/gdbarch.h  |    5 ++++-
 gdb/gdbarch.sh |    3 +++
 2 files changed, 7 insertions(+), 1 deletion(-)

Index: src/gdb/gdbarch.sh
===================================================================
--- src.orig/gdb/gdbarch.sh	2008-11-03 15:53:10.000000000 +0000
+++ src/gdb/gdbarch.sh	2008-11-03 16:05:26.000000000 +0000
@@ -710,6 +710,9 @@ M:void:record_special_symbol:struct objf
 
 # True if the list of shared libraries is one and only for all
 # processes, as opposed to a list of shared libraries per inferior.
+# When this property is true, GDB assumes that since shared libraries
+# are shared across processes, so is all code.  Hence, GDB further
+# assumes an inserted breakpoint location is visible to all processes.
 v:int:has_global_solist:::0:0::0
 EOF
 }
Index: src/gdb/gdbarch.h
===================================================================
--- src.orig/gdb/gdbarch.h	2008-11-03 15:59:16.000000000 +0000
+++ src/gdb/gdbarch.h	2008-11-03 16:05:33.000000000 +0000
@@ -812,7 +812,10 @@ extern void gdbarch_record_special_symbo
 extern void set_gdbarch_record_special_symbol (struct gdbarch *gdbarch, gdbarch_record_special_symbol_ftype *record_special_symbol);
 
 /* True if the list of shared libraries is one and only for all
-   processes, as opposed to a list of shared libraries per inferior. */
+   processes, as opposed to a list of shared libraries per inferior.
+   When this property is true, GDB assumes that since shared libraries
+   are shared across processes, so is all code.  Hence, GDB further
+   assumes an inserted breakpoint location is visible to all processes. */
 
 extern int gdbarch_has_global_solist (struct gdbarch *gdbarch);
 extern void set_gdbarch_has_global_solist (struct gdbarch *gdbarch, int has_global_solist);

      reply	other threads:[~2008-11-03 16:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28  1:28 Pedro Alves
2008-11-03 14:10 ` Pedro Alves
2008-11-03 14:30 ` Daniel Jacobowitz
2008-11-03 15:05   ` Pedro Alves
2008-11-03 15:13     ` Daniel Jacobowitz
2008-11-03 16:15       ` Pedro Alves [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=200811031614.13618.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=drow@false.org \
    --cc=gdb-patches@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