From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: Re: current bk goes BUG on ia64 when dumping core; FIXED, PATCH
Date: Tue, 07 Oct 2003 08:17:41 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106551480229104@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106533868423168@msgid-missing>
>>>>> "Roland" = Roland McGrath <roland@redhat.com> writes:
>> The new version doesn't BUG. I couldn't find the message you were
>> referring to, Roland ... However, gdb understands the core dump;
>> and objdump shows a .auxv section that looks the right size etc.
Roland> Thanks for testing this! This change is not related to the
Roland> NT_AUXV note in fact (both just happened the same week). What
Roland> you should be looking for is the readelf -l (objdump -p)
Roland> output from the core file, for the segment with vaddr
Roland> 0xa000000000010000 (GATE_ADDR). Check that its size is
Roland> PAGE_SIZE. You can also verify it in gdb while looking at the
Roland> core file by checking that e.g. "p (char *)
Roland> 0xa000000000010000" shows "ELF\177" and that "x/w
Roland> 0xa000000000010000+PAGE_SIZE-8" (substituting the right
Roland> PAGE_SIZE value) works (and shows you zeros).
All those tests pass.
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
You are lost in a maze of BitKeeper repositories, all slightly different.
prev parent reply other threads:[~2003-10-07 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-05 7:24 current bk goes BUG on ia64 when dumping core Andrew Morton
2003-10-05 7:38 ` Andrew Morton
2003-10-06 6:41 ` Roland McGrath
2003-10-06 12:34 ` Andrew Morton
2003-10-07 5:06 ` current bk goes BUG on ia64 when dumping core; FIXED, PATCH Peter Chubb
2003-10-07 5:19 ` Roland McGrath
2003-10-07 8:17 ` Peter Chubb [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=marc-linux-ia64-106551480229104@msgid-missing \
--to=peter@chubb.wattle.id.au \
--cc=linux-ia64@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.