Date: Fri, 6 Aug 2010 17:03:07 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: freebsd-stable@FreeBSD.ORG, doconnor@gsoft.com.au Subject: Re: Kernel symbol file alternate location Message-ID: <9616424E-440B-4D23-82D2-6615AC6F3CA5@gsoft.com.au> In-Reply-To: <201008060729.o767TVFZ023996@lurza.secnetix.de> References: <201008060729.o767TVFZ023996@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-2--22406450
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
On 06/08/2010, at 16:59, Oliver Fromme wrote:
>> Yeah, I don't think it's hard to move them, however I'm worried what
>> it will break :)
>>=20
>> The only thing I can see that would have to change would be kgdb so
>> it tells gdb where to find the symbols.
>=20
> That's why I suggested to place symlinks in the kernel
> directory. No change to kgdb necessary.
Ahh of course.
Although that does make it harder because you have to modify all the =
links when the old kernel is moved out of the way.
> It might even be possible to not install the symbol files
> at all, but keep them under /usr/obj, so the installkernel
> target would have to do nothing more than create symlinks.
> This could be controlled by a make.conf variable, like
> SYMLINK_SYMBOLS=3DYES ("NO" would be the existing behaviour
> of installing the actual symbol files in /boot/kernel).
Hmm, I think they would need to go elsewhere otherwise they wouldn't be =
available to people who do binary installs, hence the usefulness of bug =
reports would go down.
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
--Apple-Mail-2--22406450--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9616424E-440B-4D23-82D2-6615AC6F3CA5>