[nos-bbs] very technical question - NOS stkutil() spikes !

[maiko at pcs.mb.ca]

Hi,

Rob, Barry, Thomas, others ? This one is for you ...

In an attempt to debug a stack violation somewhere (I believe
it to be a stack violation since I'm getting alot of the dreaded
_int_malloc() SIGSEGV occurances on mbx_incom () for telnet.

I've solved the SIGSEGV, by bumping up the stack allotment in
the newproc call, BUT that's a bandaid solution ...

I've run into a very reproduceable problem where if someone
telnets into the BBS from outside, and does a Nodes, JNOS will
crash. It happens more than I would like. It's the only *bug*
that is quite frankly BUGGING the crap out of me. I'm relatively
happy with the rest of the stuff.

During the course of running the netrom dump command at the
BBS prompt, the stkutil() of the curproc is about 0x6e8, and
that is a normal value for it. HOWEVER, on one occurance, and
this really shocked me since I was not expecting it, the
stkutil() showed 0x1700 !!! Same place in the code that I
normally expect to see the smaller value.

Call it a spike if you want.

Anyway one else ever run into this ?

Maiko