Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>,
	       gdb-patches@sourceware.org
Subject: Re: [PATCH] solib-svr4: Avoid unwanted shlib internal BPs When debugging Linux kernel or u-boot
Date: Fri, 01 Jun 2012 18:05:00 -0000	[thread overview]
Message-ID: <20120601172214.GA21236@host2.jankratochvil.net> (raw)
In-Reply-To: <4FC8EC08.1060609@redhat.com>

On Fri, 01 Jun 2012 18:21:28 +0200, Pedro Alves wrote:
> --- a/gdb/solib-svr4.c
> +++ b/gdb/solib-svr4.c
> @@ -1707,7 +1707,7 @@ enable_break (struct svr4_info *info, int from_tty)
>  	}
>      }
> 
> -  if (!current_inferior ()->attach_flag)
> +  if (interp_name != NULL && !current_inferior ()->attach_flag)
>      {
>        for (bkpt_namep = bkpt_names; *bkpt_namep != NULL; bkpt_namep++)
>  	{

It has a regression in the case below.

OTOH one has to strip _start to make it a regression as with _start GDB did not
catch startup libraries even before.

This is why I suggested to omit only "__start" and "_start" but not "main" if
INTERP_NAME == NULL.

But maybe so broken systems are not so common nowadays to still care about
them.


Regards,
Jan


==> 53.C <==
#include <dlfcn.h>
#include <assert.h>
#include <stdio.h>
static void *lib;
class C {
public:
  C();
} c;
C::C() {
  lib = dlopen ("./53l.so", RTLD_NOW);
  assert(lib);
  puts("opened");
}
int main () {
  void (*fp)(void)=(void (*)(void))dlsym(lib,"l");
  assert(fp);
  fp();
}

==> 53l.C <==
#include <stdio.h>
class D {
public:
  D();
} d;
D::D() {
  puts ("in-library before-main");
}
extern "C" void l(void) {
  puts ("in-library after-main");
}

$ ./gdb-unpatched ./53 -ex 'set breakpoint pending on' -ex 'b l' -ex run 
Breakpoint 1, 0x00007ffff7dfd71e in l () from ./53l.so
(gdb) _

$ ./gdb-patched ./53 -ex 'set breakpoint pending on' -ex 'b l' -ex run 
[Inferior 1 (process 2188) exited normally]
(gdb) _


  reply	other threads:[~2012-06-01 18:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 15:01 [PATCH] solib-svr4: Avoid unwanted shlib internal BPs When debugging Linux kernel or u-boot with Abatron BDI emulator an error occurs: .. (gdb) tar remote bdi:2001 Remote debugging using bdi:2001 0xeff80050 in ?? () (gdb) mon reset (gdb) cont Continuing. Warning: Cannot insert breakpoint -1. Error accessing memory address 0xc0000000: Unknown error 4294967295 Joakim Tjernlund
2012-06-01 16:21 ` [PATCH] solib-svr4: Avoid unwanted shlib internal BPs When debugging Linux kernel or u-boot Pedro Alves
2012-06-01 18:05   ` Jan Kratochvil [this message]
2012-06-01 17:37     ` Pedro Alves
2012-06-01 18:05       ` Jan Kratochvil
2012-06-01 18:19         ` Pedro Alves
2012-06-01 19:08           ` Jan Kratochvil
2012-06-01 20:25         ` Mark Kettenis
2012-06-07  0:00       ` Maciej W. Rozycki
2012-06-08 12:10         ` Pedro Alves
2012-06-08 12:39           ` Jan Kratochvil
2012-06-08 13:07             ` Pedro Alves
2012-06-08 13:37               ` Mark Kettenis
2012-06-08 13:45                 ` Pedro Alves
2012-06-08 15:45           ` Maciej W. Rozycki
2012-06-01 18:07     ` Jan Kratochvil
2012-06-05 15:45   ` Pedro Alves

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=20120601172214.GA21236@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=Joakim.Tjernlund@transmode.se \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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