From: Andrew Cagney <ac131313@redhat.com>
To: Kip Macy <kmacy@fsmware.com>
Cc: mrdavid@leaf.lumiere.net, gdb@sources.redhat.com
Subject: Re: gdb with bigger than 2G 32bit core files
Date: Sat, 20 Mar 2004 07:00:00 -0000 [thread overview]
Message-ID: <405B5437.4010801@redhat.com> (raw)
In-Reply-To: <20040319104231.F12147@demos.bsdclusters.com>
> Yes. You need:
> --enable-64-bit-bfd
With GDB 6.1 you don't need that. With 6.0, you'd be wasting your time
- the 6.0 code base doesn't use fseek64 et.al.
For reference there's a testcase (bigcore.exp) that is known to pass on
certain GNU/Linux variants (RHEL for instance).
Andrew
>>>
>>> hi,
>>>
>>> has anyone been able to analyze bigger than 2 gig core files?
>>>
>>> i am trying to analyze core files produced by a 32bit x86 linux 2.4 box
>>> with the O_LARGEFILE core patch like this :
>>>
>>> file = filp_open(corename, O_CREAT | 2 | O_NOFOLLOW | O_LARGEFILE, 0600);
>>>
>>> i know it can be done with linux 2.6 on 64bit arch box...
>>>
>>>
>>>
>>> ~david
prev parent reply other threads:[~2004-03-19 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040319101508.Y66700-100000@leaf.lumiere.net>
2004-03-20 6:19 ` Kip Macy
2004-03-20 7:00 ` Andrew Cagney [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=405B5437.4010801@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kmacy@fsmware.com \
--cc=mrdavid@leaf.lumiere.net \
/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