On Thu 26 Mar 1998, Michael Brandt wrote:
> > Can you also try 'nm /netbsd' and look in which function the
> > program really is?
> 
> How do I do that? `nm' just gives me a very long list of symbols. Apart from
> that, isn't it visible in the stack trace in which funtion the kernel crashed?

No, the stack trace does not always give this info. The only way to find it
out in that case is to use 'nm /netbsd | less'. Just lookup the 2 symbols
surrounding the PC. the one with the lowest value is the one you're looking
for.

[ ... ]
> > O, and do you use a standard config? If not, what are the diffs
> > to the config it was derived from?
> 
> No, I didn't use a standard config. Mine is a collection from different sources
> that evolved over time. I include it as an attachment as well as the slightely
> changed include file I use.

I undusted my TT030 tonight and tested a kernel I made with your config and
it just seems to work... Do you mind if I send you that kernel through email?

Leo.