From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>,
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, 08 Jun 2012 13:07:00 -0000 [thread overview]
Message-ID: <4FD1F902.5000705@redhat.com> (raw)
In-Reply-To: <20120608123847.GA13337@host2.jankratochvil.net>
On 06/08/2012 01:38 PM, Jan Kratochvil wrote:
> I still do not see why 'main' was not left there as it would not hurt and it
> could help.
The original patch was trivial, and a one liner. I preferred not requiring
bigger changes and risk needing to require copyright assignment for that patch.
Then, GDB has not been trapping on "main", but on "_start" for static binaries
for a long time, so that even feels like a separate "feature" to me. I even feel
like we could/should drop the "_start/main" fallback from svr4 handling. It's
just historic at this point, as far as I could ascertain. If those are
really needed on some system, then a comment in the code mentioning such system
is warranted.
> OTOH some real world case (some incompatible ld.so state point
> name + build) should be given first before finding a solution for it.
That's my view too. And if that case would be found, we might find
a better solution instead of trapping _start or main.
--
Pedro Alves
next prev parent reply other threads:[~2012-06-08 13:07 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
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 [this message]
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=4FD1F902.5000705@redhat.com \
--to=palves@redhat.com \
--cc=Joakim.Tjernlund@transmode.se \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=macro@codesourcery.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