Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Oct 2001 10:05:07 +0930
From:      Greg Lehey <grog@FreeBSD.org>
To:        John Baldwin <jhb@FreeBSD.org>
Cc:        FreeBSD-arch@FreeBSD.ORG, Nate Williams <nate@yogotech.com>, Dag-Erling Smorgrav <des@ofug.org>
Subject:   Re: /usr/src/sys/scripts?
Message-ID:  <20011020100507.Z60412@wantadilla.lemis.com>
In-Reply-To: <XFMail.011019084241.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Fri, Oct 19, 2001 at 08:42:41AM -0700
References:  <20011019101946.E60412@wantadilla.lemis.com> <XFMail.011019084241.jhb@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 19 October 2001 at  8:42:41 -0700, John Baldwin wrote:
>
> On 19-Oct-01 Greg Lehey wrote:
>> On Friday, 19 October 2001 at  1:04:12 +0200, Dag-Erling Smorgrav wrote:
>>> Nate Williams <nate@yogotech.com> writes:
>>>> Most folks will probably not analyze the crashdumps, or they will copy
>>>> them off somewhere else so they can free up /var/crash for the next
>>>> crashdump, so I'd say stick .gdbinit somewhere else.
>>>
>>> /usr/src/share/misc or /usr/src/sys/conf might be good choices then.
>>> /usr/src/sys/scripts sounds like a good idea, I don't like the idea of
>>> creating a new directory just for one teeny little file.
>>
>> No, there are a number of files in there, and I expect more to
>> arrive.  I'm prepared to discuss the point, though.  /sys/scripts has
>> the advantage that it's compatible with BSD/OS, which I don't suppose
>> we have to over-emphasize.
>
> One thing I would suggest is to create several .gdbinit.foo files for different
> functionality so that one can create a custom .gdbinit simply by including the
> desired set of .gdbinit.foo files.  Thus making it easier for people who
> already have a hacked .gdbinit to use these new functions as well.

Yes, that's my plan.

> Note that some of the functions may very well end up being very MD
> (such as the manual stack traces of other pids by examining the
> stack, etc.) so we might want to think about a way of handling MD
> scripts vs. MI scripts.

I'm open to suggestions.  One might really be to put the MD stuff in
the <arch>/conf file, as DES suggested.

Greg
--
See complete headers for address and phone numbers

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011020100507.Z60412>