On 2003.11.10, Kenneth Snyder <[EMAIL PROTECTED]> wrote:
> Here's the output from the debugger:
> [...]
> trace in nsmain.c: 369 i = ns_fork();
> trace in fork.c: 64 return fork();
> [10/Nov/2003:18:24:05][20214.1][] Notice: config.tcl: starting to read
> config file...
> [10/Nov/2003:18:24:05][20214.1][] Notice: right before SLC...
> trace in fork.c: 66 }
> trace in nsmain.c: 370 if (i < 0) {
> trace in nsmain.c: 373 if (i > 0) {
> trace in nsmain.c: 374 return 0;
> trace in nsmain.c: 648 }
> trace in main.c: 65 }
>
> execution completed
> (dbx)
It's been at least 6 years since I actively sat at at an AIX system --
and it was an AIX 3.2.5 system at that -- so I can't remember the exact
way to do it, but you need to tell dbx to follow forks. The debug
output you included isn't very interesting, since the bad stuff happens
in the process after it forks, which we're not seeing here ...
However, I can already guess from the previous email you sent what the
problem might be:
> Illegal instruction in . at 0x0 ($t1)
> 0x00000000 00000000 Invalid opcode.
Null opcode? Sounds like the stack got smashed. What's your stacksize
set to in your config.tcl?
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
