From: Doug Evans <dje@google.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Tristan Gingold <gingold@adacore.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: AIX DWARF debugging sections
Date: Tue, 06 Oct 2015 00:30:00 -0000 [thread overview]
Message-ID: <CADPb22RhyhWrxLu2vy-TOp7ua97BWBJ6Loa9puoSFiYZq82NBg@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnyk5YtqV=kjDa=MVJup7wdt2s=BdADAVAvg+D9rp9ihxfA@mail.gmail.com>
On Fri, Oct 2, 2015 at 3:35 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
> On Fri, Oct 2, 2015 at 5:32 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>>> > On 25 Sep 2015, at 16:53, David Edelsohn <dje.gcc@gmail.com> wrote:
>>> >
>>> > Initial AIX support for DWARF did not include location lists, debug
>>> > frame, and macinfo. Support was added in a later update.
>>> >
>>> > xcoffread defines most of the sections -- including some that were
>>> > included later and omitting some that were included in the initial
>>> > implementation.
>>> >
>>> > Does anyone know why pbtyp and mac are not define?
>>>
>>> AFAIK, .debug_pubtypes are not read by gdb.
>>>
>>> > I'm not sure if
>>> > AIX .dwamac is macinfo or macro or both.
>>> >
>>> > Thanks, David
>>>
>>> Your patch looks ok to me, but should be approved by
>>> a global maintainer.
>>
>> It looks odd to me that two entries would have the same name.
>> Wouldn't it cause GDB to decode the same section both as .debug_macinfo
>> and .debug_macro?
>
> Because the AIX section does not use the standard name, I am unsure
> which it represents. The documentation only states "dwmac", which
> could expand to either name.
>
> Thanks, David
Yeah, I think we need to figure out which one it is.
next prev parent reply other threads:[~2015-10-06 0:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 14:53 David Edelsohn
2015-09-28 13:41 ` Tristan Gingold
2015-10-02 21:32 ` Joel Brobecker
2015-10-02 22:35 ` David Edelsohn
2015-10-06 0:30 ` Doug Evans [this message]
2015-10-06 16:52 ` Joel Brobecker
2015-10-06 16:55 ` David Edelsohn
2015-10-06 18:24 ` David Edelsohn
2015-10-06 20:00 ` Doug Evans
2015-10-07 12:49 ` David Edelsohn
2015-10-10 0:04 ` Joel Brobecker
[not found] ` <CADPb22QmuPeP_QBDNWA4iSi1jsnTvAiAurV8HWGCAYnPoMr+wg@mail.gmail.com>
2015-10-10 2:58 ` David Edelsohn
2015-10-12 15:50 ` Joel Brobecker
2015-10-12 17:41 ` David Edelsohn
2015-10-12 18:34 ` Joel Brobecker
2015-10-13 15:33 ` David Edelsohn
2015-10-13 16:45 ` Joel Brobecker
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=CADPb22RhyhWrxLu2vy-TOp7ua97BWBJ6Loa9puoSFiYZq82NBg@mail.gmail.com \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=dje.gcc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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