Date: Tue, 19 Apr 2005 23:54:39 -0700 From: Peter Wemm <peter@wemm.org> To: freebsd-amd64@freebsd.org Subject: Re: INCLUDE_CONFIG_FILE broken? Message-ID: <200504192354.39601.peter@wemm.org> In-Reply-To: <8664yndm6v.fsf@xps.des.no> References: <E1DEjZu-0007MN-RR@cs1.cs.huji.ac.il> <20050416093349.I5888@epsplex.bde.org> <8664yndm6v.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 16 April 2005 03:56 am, Dag-Erling Sm=F8rgrav wrote: > Bruce Evans <bde@zeta.org.au> writes: > > You could just use the existing mechanism __IDSTRING(), preferably > > after fixing it to actually work. (__IDSTRING() generates invalid > > asm if the string has a newline in it. Among other bugs, this > > breaks most uses of __COPYRIGHT().) > > __IDSTRING() places the string in a separate section. By default, > strings(1) only extracts strings from code and data sections, so the > good old 'strings -n 3 kernel | grep \^___' wouldn't work. Not a big > deal, but still a slight POLA breach. True, but 'strings -a' will do the entire file... Or we can do what linux does and insert things into any section we like=20 by using the gas .incbin "filename" construct. I'm not sure if I like that any more than using objcopy to=20 insert a section. =2D-=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504192354.39601.peter>