This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC][PATCH 0/3] readelf and libbfd: Add Extended Numbering Support for ELF

From: Daniel Jacobowitz <dan at codesourcery dot com>
To: Ian Lance Taylor <iant at google dot com>
Cc: Daisuke HATAYAMA <d dot hatayama at jp dot fujitsu dot com>, binutils at sourceware dot org
Date: Sun, 17 Jan 2010 09:16:54 -0500
Subject: Re: [RFC][PATCH 0/3] readelf and libbfd: Add Extended Numbering Support for ELF
References: <20100115.114307.193710254.d.hatayama@jp.fujitsu.com> <mcrhbqnweix.fsf@dhcp-172-17-9-151.mtv.corp.google.com>

On Fri, Jan 15, 2010 at 07:53:26AM -0800, Ian Lance Taylor wrote:
> You mean that they currently have a 2 byte length.
> 
> I very sincerely hope that we never have an ELF file with more than
> 4,294,967,295 segments.
> 
> It's hard enough to understand having more than 65,535 segments
> (sections, sure; segments?).

It's mainly, as he wrote later, for core files.  I'm surprised you
haven't complained about this limitation yourself :-)  If your thread
stacks were allocated with guard pages, a core dump with over 64k threads
should have over 64k segments.

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: [RFC][PATCH 0/3] readelf and libbfd: Add Extended Numbering Support for ELF
  - From: Daisuke HATAYAMA
- Re: [RFC][PATCH 0/3] readelf and libbfd: Add Extended Numbering Support for ELF
  - From: Ian Lance Taylor

References:
- [RFC][PATCH 0/3] readelf and libbfd: Add Extended Numbering Support for ELF
  - From: Daisuke HATAYAMA
- Re: [RFC][PATCH 0/3] readelf and libbfd: Add Extended Numbering Support for ELF
  - From: Ian Lance Taylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]