Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org, Kevin Buettner <kevinb@redhat.com>
Subject: [rfa] Extra warning in solib-svr4
Date: Fri, 30 Mar 2007 14:45:00 -0000	[thread overview]
Message-ID: <20070330144519.GC14014@caradoc.them.org> (raw)

Suppose you take a static linked program, strip it, and run it under
GDB.  You'll get this warning:

warning: shared library handler failed to enable breakpoint

You can reproduce this without stripping - you need to have no .interp
section and no functions named _start or main, that's all.  So this
actually came up when using KGDB to debug a Linux kernel.

The shared library breakpoint is generally not important in this
case.  It's more important if there was a .interp but something went
wrong while trying to load the referenced executable; that's got a
separate warning:

      warning (_("Unable to find dynamic linker breakpoint function.\n"
               "GDB will be unable to debug shared library initializers\n"
               "and track explicitly loaded dynamic code."));

I think the more general warning is not useful, since it has a high
correlation with non-shared programs.  OK to remove it?

-- 
Daniel Jacobowitz
CodeSourcery

2007-03-30  Daniel Jacobowitz  <dan@codesourcery.com>

	* solib-svr4.c (enable_break): Simplify return value.
	(svr4_solib_create_inferior_hook): Do not warn if enable_break fails.

Index: solib-svr4.c
===================================================================
RCS file: /cvs/src/src/gdb/solib-svr4.c,v
retrieving revision 1.61
diff -u -p -r1.61 solib-svr4.c
--- solib-svr4.c	9 Jan 2007 17:58:58 -0000	1.61
+++ solib-svr4.c	30 Mar 2007 14:39:46 -0000
@@ -979,8 +979,6 @@ exec_entry_point (struct bfd *abfd, stru
 static int
 enable_break (void)
 {
-  int success = 0;
-
 #ifdef BKPT_AT_SYMBOL
 
   struct minimal_symbol *msymbol;
@@ -1146,13 +1144,9 @@ enable_break (void)
 	  return 1;
 	}
     }
-
-  /* Nothing good happened.  */
-  success = 0;
-
 #endif /* BKPT_AT_SYMBOL */
 
-  return (success);
+  return 0;
 }
 
 /*
@@ -1357,10 +1351,7 @@ svr4_solib_create_inferior_hook (void)
     }
 
   if (!enable_break ())
-    {
-      warning (_("shared library handler failed to enable breakpoint"));
-      return;
-    }
+    return;
 
 #if defined(_SCO_DS)
   /* SCO needs the loop below, other systems should be using the


             reply	other threads:[~2007-03-30 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30 14:45 Daniel Jacobowitz [this message]
2007-03-30 19:02 ` Mark Kettenis
2007-04-10  6:53 ` Kevin Buettner
2007-04-10 11:51   ` Daniel Jacobowitz

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=20070330144519.GC14014@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@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