From: Andrew Cagney <ac131313@redhat.com>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] 64-bit bigcore.exp fixes
Date: Fri, 24 Sep 2004 18:48:00 -0000 [thread overview]
Message-ID: <41546B5A.7080308@redhat.com> (raw)
In-Reply-To: <415465A0.nail1EK21DHQX@mindspring.com>
> Okay, approved.
It's in.
I forgot to mention that Dave Anderson (@redhat) came up with the seek
trick, I added his name to the ChangeLog before committing.
thanks,
Andrew
> 2004-09-24 Andrew Cagney <cagney@redhat.com>
>
> * gdb.base/bigcore.exp (extract_heap): If the expect "file size"
> command fails, assume things will work.
> * gdb.base/bigcore.c: Include <sys/stat.h> and <fcntl.h>.
> (_GNU_SOURCE): Define.
> (print_unsigned, print_hex): Change parameter to "long long".
> (print_byte_count): New function, use to print byte counts.
> (large_off_t, large_lseek, O_LARGEFILE): Define dependant on
> O_LARGEFILE.
> (main): Compute an upper bound on a corefile in max_core_size.
> Limit memory chunk size to max_core_size. Limit total memory
> allocated to max_core_size.
prev parent reply other threads:[~2004-09-24 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 13:51 Andrew Cagney
2004-09-24 18:21 ` Michael Chastain
2004-09-24 18:48 ` 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=41546B5A.7080308@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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