From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: tromey@redhat.com
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch] Fix separate-debug with non-unique section names (PR 11409)
Date: Wed, 24 Mar 2010 19:23:00 -0000 [thread overview]
Message-ID: <201003241923.o2OJN6vL028899@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <m339zpk0gg.fsf@fleche.redhat.com> (message from Tom Tromey on Wed, 24 Mar 2010 13:02:07 -0600)
> From: Tom Tromey <tromey@redhat.com>
> Date: Wed, 24 Mar 2010 13:02:07 -0600
>
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> Jan> gdb-7.1 is now broken for example for debugging /usr/bin/emacs due to:
> Jan> http://sourceware.org/bugzilla/show_bug.cgi?id=11409
> Jan> [22] .data PROGBITS 00000000007fe8a0 1fe8a0 215068 00 WA 0 0 32
> Jan> [23] .data PROGBITS 0000000000a13920 413920 68c6e0 00 WA 0 0 32
>
> Jan> 2010-03-23 Jan Kratochvil <jan.kratochvil@redhat.com>
> Jan> * symfile.c (addr_info_make_relative): Move sect declaration to the
> Jan> outer block. Initialize it to NULL. Prefer SECT->next more than
> Jan> bfd_get_section_by_name.
>
> This patch seems to assume that all sections of the same name will be
> next to each other in the section_addr_info. Why is it ok to make this
> assumption?
That assumption is false, at least in general. I have an
OpenBSD/mips64el emacs binary that has two .data sections that aren't
adjacent.
next prev parent reply other threads:[~2010-03-24 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 20:57 Jan Kratochvil
2010-03-24 19:02 ` Tom Tromey
2010-03-24 19:23 ` Mark Kettenis [this message]
2010-03-24 20:09 ` Jan Kratochvil
2010-03-24 20:18 ` Daniel Jacobowitz
2010-03-24 20:33 ` Jan Kratochvil
2010-03-24 20:37 ` Tom Tromey
2010-03-25 14:59 ` Jan Kratochvil
2010-03-25 20:00 ` Tom Tromey
2010-03-25 20:38 ` Jan Kratochvil
2010-04-21 20:03 ` Tom Tromey
2010-04-22 23:22 ` Jan Kratochvil
2010-03-24 20:43 ` 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=201003241923.o2OJN6vL028899@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@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