Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: [rfc] Print solib events in mi-mode
Date: Tue, 08 Jul 2003 20:35:00 -0000	[thread overview]
Message-ID: <062401c34590$97cd09b0$0202040a@catdog> (raw)

What do you think of something like this?  When stop-on-solib-events is set,
this will print the reason as being a shared-lib-event.

Our Eclipse team wants to be able to set breakpoints in shared libraries
that aren't loaded yet.  If they get notification of shlib-events, then they
can re-examine the list of loaded libraries and set any breakpoints that
have been enabled in the project's libs.

cheers,

Kris

$ cvs diff -u breakpoint.c
Index: breakpoint.c
===================================================================
RCS file: /cvs/src/src/gdb/breakpoint.c,v
retrieving revision 1.125
diff -u -r1.125 breakpoint.c
--- breakpoint.c        2 Jul 2003 16:24:00 -0000       1.125
+++ breakpoint.c        8 Jul 2003 20:32:50 -0000
@@ -2039,8 +2039,10 @@
       /* Did we stop because the user set the stop_on_solib_events
         variable?  (If so, we report this as a generic, "Stopped due
         to shlib event" message.) */
-      printf_filtered ("Stopped due to shared library event\n");
-      return PRINT_NOTHING;
+      ui_out_text (uiout, "\nShared library event ");
+      if (ui_out_is_mi_like_p (uiout))
+       ui_out_field_string (uiout, "reason", "shared-lib-event");
+      return PRINT_SRC_ONLY;
       break;

     case bp_thread_event:



             reply	other threads:[~2003-07-08 20:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08 20:35 Kris Warkentin [this message]
2003-07-08 21:02 ` Andrew Cagney
2003-07-09 12:24   ` Kris Warkentin
2003-07-09 15:09     ` Daniel Jacobowitz
2003-07-09 15:38       ` Kris Warkentin
2003-07-09 16:24         ` Daniel Jacobowitz
2003-07-09 17:29           ` Kris Warkentin
2003-07-09 17:41             ` Kevin Buettner
2003-07-09 17:49               ` Kris Warkentin
2003-07-09 18:01                 ` Kris Warkentin
2003-07-09 18:05                   ` Daniel Jacobowitz
2003-07-09 18:21                     ` Kris Warkentin
2003-07-09 18:30                       ` Daniel Jacobowitz
2003-07-09 19:12                         ` Kris Warkentin
2003-07-09 19:46                           ` Daniel Jacobowitz
2003-07-09 20:00                             ` Kris Warkentin
2003-07-09 20:03                               ` Daniel Jacobowitz
2003-07-18 16:12                 ` Andrew Cagney
2003-07-09 20:38 ` Jason Molenda
2003-07-10 12:23   ` Kris Warkentin
2003-07-10 16:33   ` Andrew Cagney

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='062401c34590$97cd09b0$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=gdb@sources.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