From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
jdike@addtoit.com, tony.luck@intel.com, mhiramat@redhat.com
Subject: Re: [RFC, PATCH 4/4] elf_core_dump(): Add extended numbering support
Date: Tue, 15 Dec 2009 16:34:01 +0800 [thread overview]
Message-ID: <2375c9f90912150034w430dcb07od76273d08ba1b06d@mail.gmail.com> (raw)
In-Reply-To: <2375c9f90912142356s6bd6708fi1cb04e6ff0c72c4a@mail.gmail.com>
On Tue, Dec 15, 2009 at 3:56 PM, Américo Wang <xiyou.wangcong@gmail.com> wrote:
> On Tue, Dec 15, 2009 at 10:41 AM, Daisuke HATAYAMA
> <d.hatayama@jp.fujitsu.com> wrote:
>> The current ELF dumper implementation can produce broken corefiles
>> if program headers exceed 65535. This number is determined by the
>> number of vmas which the process have. In particular, some extreme
>> programs may use more than 65535 vmas. (If you google max_map_count,
>> you can find some users facing this problem.) This kind of program
>> never be able to generate correct coredumps.
>>
>> This patch implements ``extended numbering'' that uses sh_info
>> field of the first section header instead of e_phnum field in order
>> to represent upto 4294967295 vmas.
>>
>> This is supported by AMD64-ABI(http://www.x86-64.org/documentation.html)
>> and Solaris(http://docs.sun.com/app/docs/doc/817-1984/). Of course,
>> we are preparing patches for gdb and binutils.
>>
>> Signed-off-by: Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>
>
>
> Hi,
>
> Can you reorder your patches please?
> Your patch 0/4 depends on 1/4, I am afraid. :-/
>
Oops!
Ignore this, I misread the subject. 4/4 depends on 1/4,
which is fine. :)
next prev parent reply other threads:[~2009-12-15 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 2:41 Daisuke HATAYAMA
2009-12-15 7:56 ` Américo Wang
2009-12-15 8:34 ` Américo Wang [this message]
2009-12-15 8:27 ` Américo Wang
2009-12-16 2:24 ` Daisuke HATAYAMA
2009-12-15 14:09 ` Andi Kleen
2009-12-16 0:30 ` KOSAKI Motohiro
2009-12-16 2:32 ` Daisuke HATAYAMA
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=2375c9f90912150034w430dcb07od76273d08ba1b06d@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=d.hatayama@jp.fujitsu.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®