From: Ken Werner <ken@linux.vnet.ibm.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>, gdb@sourceware.org
Subject: Re: [patch] Use mmap instead of obstack_alloc for dwarf debug sections.
Date: Thu, 18 Jun 2009 09:08:00 -0000 [thread overview]
Message-ID: <200906180908.n5I983Ft016002@d06av04.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <8ac60eac0906161407s6498913cu5e50e930d599be77@mail.gmail.com>
Paul Pluzhnikov wrote:
> On Tue, Jun 16, 2009 at 1:58 PM, Tom Tromey<tromey@redhat.com> wrote:
>
>> This patch ok.
>
> So committed.
>
> Thanks,
Hi,
I noticed gdb/dwarf2-frame.c:1922 (and :1950) calls dwarf2_get_section_info
with unsigned long* (5th argument). The function expects a bfd_size_type *
(a pointer to an unsigned long long on my machine). Thus the compiler issues
a warning and the gdb build fails because of -Werror. Is it sufficient to
just cast to (bfd_size_type *) or am I missing something?
Regards
-ken
next parent reply other threads:[~2009-06-18 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090527001157.934BD76BC0@localhost>
[not found] ` <m3iqjmt4bn.fsf@fleche.redhat.com>
[not found] ` <8ac60eac0905280956v79d9a84apad9a4370212283b9@mail.gmail.com>
[not found] ` <m3vdniw74z.fsf@fleche.redhat.com>
[not found] ` <8ac60eac0906101839t4d3978fyc1c6d3b3e2eccb6e@mail.gmail.com>
[not found] ` <8ac60eac0906101842y2d2fc9fco331cb4336d9508d0@mail.gmail.com>
[not found] ` <m3zlc80yxc.fsf@fleche.redhat.com>
[not found] ` <8ac60eac0906161342m67c30151lc7f685e0eb36e41f@mail.gmail.com>
[not found] ` <m3y6rrzyi7.fsf@fleche.redhat.com>
[not found] ` <8ac60eac0906161407s6498913cu5e50e930d599be77@mail.gmail.com>
2009-06-18 9:08 ` Ken Werner [this message]
2009-06-18 9:20 ` Ken Werner
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=200906180908.n5I983Ft016002@d06av04.portsmouth.uk.ibm.com \
--to=ken@linux.vnet.ibm.com \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.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