From: Daniel Jacobowitz <drow@false.org>
To: Alan Modra <amodra@bigpond.net.au>
Cc: gdb@sources.redhat.com
Subject: Re: PR 2014, 2007, 1968, 1945, 1935, 1865, 1823
Date: Thu, 27 Oct 2005 02:53:00 -0000 [thread overview]
Message-ID: <20051027025335.GA11566@nevyn.them.org> (raw)
In-Reply-To: <20051027025052.GT17244@bubble.grove.modra.org>
On Thu, Oct 27, 2005 at 12:20:52PM +0930, Alan Modra wrote:
> On Wed, Oct 26, 2005 at 10:01:24PM -0400, Daniel Jacobowitz wrote:
> > Oh, while you're in the area: ISTR finding that BFD was missing
> > O_LARGEFILE somewhere that GDB had it. So if GDB opened the core file,
> > and then BFD closed and reopened it, the open would fail.
>
> Yes, there was a silly check in bfd_cache_lookup_worker that tested for
> abfd->where being in unsigned long range. That's gone, but I guess
> there might be other places similarly broken.
No, I meant this literally: gdb/corelow.c:bfd_open uses O_LARGEFILE,
and nothing in BFD does. This means that BFD can't open 4GB files on
some 32-bit environments.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-10-27 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 1:14 Alan Modra
2005-10-27 2:01 ` Daniel Jacobowitz
2005-10-27 2:51 ` Alan Modra
2005-10-27 2:53 ` Daniel Jacobowitz [this message]
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=20051027025335.GA11566@nevyn.them.org \
--to=drow@false.org \
--cc=amodra@bigpond.net.au \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).