From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] remote: Avoid unwanted shlib internal BPs When debugging Linux kernel or u-boot with Abatron BDI emulator an error occurs:
Date: Fri, 01 Jun 2012 14:48:00 -0000 [thread overview]
Message-ID: <OF322378AB.B2F2176F-ONC1257A10.0051062C-C1257A10.00514CCD@transmode.se> (raw)
In-Reply-To: <4FC8D466.2020203@redhat.com>
Pedro Alves <palves@redhat.com> wrote on 2012/06/01 16:40:38:
>
> On 06/01/2012 03:38 PM, Joakim Tjernlund wrote:
>
> >> GDB has no special knowledge of the Linux kernel, nor of u-boot.
> >> > A GNU/Linux targeted GDB (*-*-linux-gnu) recognizes, and knows how to
> >> > debug user space applications. If the kernel binary or the u-boot binary
> >> > look very much like GNU/Linux user space programs, the *-*-linux-gnu targeted
> >> > GDB will assume that's what they are. If you used a bare metal elf/eabi
> >> > targeted GDB, which is really what those programs are, you'd not see this.
> >
>
> >
> > Yes you would, the error comes from this in solibsvr4.c:
>
> > static const char * const bkpt_names[] =
> > {
> > "_start",
> > "__start",
> > "main",
> > NULL
> > };
>
>
> No you wouldn't, because solib-svr4 is not used (or even compiled in)
> on a bare metal targeted GDB.
Ah, right you are. So this "just" hits svr4 users. Anyhow, its is a problem and
needs to be fixed(in svr4 lib I guess)
Jocke
next prev parent reply other threads:[~2012-06-01 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 13:37 Joakim Tjernlund
2012-06-01 14:08 ` Pedro Alves
2012-06-01 14:39 ` Joakim Tjernlund
2012-06-01 14:40 ` Pedro Alves
2012-06-01 14:48 ` Joakim Tjernlund [this message]
[not found] ` <OF322378AB.B2F2176F-ONC1257A10.0051062C-C1257A10.00514CCD@LocalDomain>
2012-06-01 14:49 ` Joakim Tjernlund
2012-06-01 14:53 ` Joakim Tjernlund
2012-06-01 14:56 ` Pedro Alves
2012-06-01 15:01 ` Joakim Tjernlund
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=OF322378AB.B2F2176F-ONC1257A10.0051062C-C1257A10.00514CCD@transmode.se \
--to=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