Re: somebody has broken sysctlbyname() in -current

1999-05-14 Thread Daniel C. Sobral
Stefan Bethke wrote: > > Any pointer on Forth literature/web pages would be appreciated, especially > if it's not the ANSI standard (I've looked at it, and it is that: a > standard, not a reference manual or a tutorial). My Forth knowledge is > rather rusty, I realised... last time I remember I w

Re: somebody has broken sysctlbyname() in -current

1999-05-12 Thread Andrzej Bialecki
On Wed, 12 May 1999, Stefan Bethke wrote: > Any pointer on Forth literature/web pages would be appreciated, especially > if it's not the ANSI standard (I've looked at it, and it is that: a > standard, not a reference manual or a tutorial). My Forth knowledge is > rather rusty, I realised... last

Re: somebody has broken sysctlbyname() in -current

1999-05-12 Thread Stefan Bethke
Andrzej Bialecki wrote: > On Sat, 8 May 1999, Peter Wemm wrote: > >> It's interesting that the ANSI emulation in loader(8) is good enough to >> do full-screen displays. It still seems to make sense to move >> userconfig-like functionality into the pre-kernel stages including >> moving config(8)'

Re: somebody has broken sysctlbyname() in -current

1999-05-11 Thread Andrzej Bialecki
On Sat, 8 May 1999, Peter Wemm wrote: > It's interesting that the ANSI emulation in loader(8) is good enough to do > full-screen displays. It still seems to make sense to move userconfig-like > functionality into the pre-kernel stages including moving config(8)'s hints > to a loaded and parsed fi

Re: somebody has broken sysctlbyname() in -current

1999-05-08 Thread Daniel C. Sobral
Peter Wemm wrote: > > Well, if you look at userconfig.c, you'll notice that very few people > understand/maintain that code either. The most common changes are adding > or removing device descriptions in a table, and that should be pretty > much the same no matter what language it's written in...

Re: somebody has broken sysctlbyname() in -current

1999-05-08 Thread Peter Wemm
"Daniel C. Sobral" wrote: > Peter Wemm wrote: > > > > It's interesting that the ANSI emulation in loader(8) is good enough to do > > full-screen displays. It still seems to make sense to move userconfig-like > > functionality into the pre-kernel stages including moving config(8)'s hints > > to a

Re: somebody has broken sysctlbyname() in -current

1999-05-08 Thread Daniel C. Sobral
Peter Wemm wrote: > > It's interesting that the ANSI emulation in loader(8) is good enough to do > full-screen displays. It still seems to make sense to move userconfig-like > functionality into the pre-kernel stages including moving config(8)'s hints > to a loaded and parsed file. Forth, bah..

Re: somebody has broken sysctlbyname() in -current

1999-05-07 Thread Peter Wemm
Andrzej Bialecki wrote: > On Sat, 8 May 1999, Peter Wemm wrote: > > > "Jordan K. Hubbard" wrote: > > > > sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); > > > > > > Sorry for the vague first bug report; I hadn't collected a reasonable > > > crashdump yet. It's in sysctl_machdep_

Re: somebody has broken sysctlbyname() in -current

1999-05-07 Thread Andrzej Bialecki
On Sat, 8 May 1999, Peter Wemm wrote: > "Jordan K. Hubbard" wrote: > > > sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); > > > > Sorry for the vague first bug report; I hadn't collected a reasonable > > crashdump yet. It's in sysctl_machdep_uc_devlist(), specifically > > where i

Re: somebody has broken sysctlbyname() in -current

1999-05-07 Thread Jordan K. Hubbard
> Should be fixed as of a few minutes ago in userconfig.c: > > revision 1.140 > date: 1999/05/07 16:54:50; author: peter; state: Exp; lines: +34 -2 > Yet another kludge to maintain the isa_device illusion, this time malloc > an isa_driver and name pointer so the uc_d

Re: somebody has broken sysctlbyname() in -current

1999-05-07 Thread Peter Wemm
"Jordan K. Hubbard" wrote: > > sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); > > Sorry for the vague first bug report; I hadn't collected a reasonable > crashdump yet. It's in sysctl_machdep_uc_devlist(), specifically > where it copies id->id_driver->name into a temporary stack

Re: somebody has broken sysctlbyname() in -current

1999-05-07 Thread Peter Wemm
"Jordan K. Hubbard" wrote: > > sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); > > Sorry for the vague first bug report; I hadn't collected a reasonable > crashdump yet. It's in sysctl_machdep_uc_devlist(), specifically > where it copies id->id_driver->name into a temporary stack

Re: somebody has broken sysctlbyname() in -current

1999-05-07 Thread Jordan K. Hubbard
> sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); Sorry for the vague first bug report; I hadn't collected a reasonable crashdump yet. It's in sysctl_machdep_uc_devlist(), specifically where it copies id->id_driver->name into a temporary stack variable. First time through, this t

somebody has broken sysctlbyname() in -current

1999-05-07 Thread Jordan K. Hubbard
How to repeat symptoms: boot -c kget Watch your system panic when kget does a: sysctlbyname("machdep.uc_devlist", buf, &len, NULL, NULL); where len has been properly fetched in a previous syctlbyname() call (1526 bytes, in my test case) and buf allocated appropriately. System