Subject: Re: bin/33909: modload fails with "section .eh_frame ... overlaps section .data"
To: None <gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,>
From: David Laight <david@l8s.co.uk>
List: netbsd-bugs
Date: 07/05/2006 21:00:07
The following reply was made to PR bin/33909; it has been noted by GNATS.

From: David Laight <david@l8s.co.uk>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: bin/33909: modload fails with "section .eh_frame ... overlaps section .data"
Date: Wed, 5 Jul 2006 22:06:41 +0100

 On Mon, Jul 03, 2006 at 09:45:00PM +0000, khym@azeotrope.org wrote:
 > >Number:         33909
 > >Category:       bin
 > >Synopsis:       modload fails with "section .eh_frame ... overlaps section .data"
 > 
 > 	On amd64-current with Feb 19 kernel and userland:
 > ld: section .eh_frame [ffffffff80651768 -> ffffffff8065261f] overlaps section .data [ffffffff806525c0 -> ffffffff80652a27]
 
 Actually you probably don't want to build kernels and loadable modules
 with the .eh_frame section (not unless we demand-load their pages!).
 
 If you read about the decisions made when the gcc amd64 port was done, they
 decided to include the .eh_frame section in all builds because the data
 wouldn't usually get loaded so the section size didn't matter!
 
 Linux kernels builds run with the compiler option to exclude the section.
 
 (of course, this is a differect issue to the overlapping section one...)
 
 	David
 
 -- 
 David Laight: david@l8s.co.uk