>   394       nsconf.nsd = (char *) Tcl_GetNameOfExecutable();
> (dbx) next
> trace in nsmain.c:  395       NsConfigEval(config, argc, argv, optind);
> stopped in Ns_Main at line 395 in file
> "/aolserver_devel/aolserver-4.0-beta10-src/nsd/nsmain.c" ($t1)
>   395       NsConfigEval(config, argc, argv, optind);
> (dbx) next
>
> Illegal instruction in . at 0x0 ($t1)
> 0x00000000 00000000       Invalid opcode.
> (dbx) next


This means that within NsConfigEval there is an instruction that made
the code jump to an address which points to nothing.  Sometime this means
that the pointer was freed. Or maybe some dynamic library was unloaded or
maybe even failed to load properly and was never reported.  And so
the address to a function now points to nothing.

What you need to do is follow into NsConfigEval (e.g.  instead of doing next
you need to do "step" to go into NsConfigEval) and then do next again.
This will get you closer to your problem.

You may also need to do "stepi" to start looking at assembler instructions
which can give you more of a clue to whats happening if the step and next
instructions are not enough.

The worse scenario is for you to have to get an assembler listing of
your code to match the debugger output with your assembler listing so
you can find out the exact line of code it is failing.

good luck

PS:  since this is in NsConfigEval , to me it sounds like there is
some problem with your config file that AOLserver is not checking properly
and its just barfing at it.  For grins try out the default config file
and see if you have the problem still (not sure if you already tried this).


>
> Illegal instruction in . at 0x0 ($t1)
> 0x00000000 00000000       Invalid opcode.
> (dbx) next
>
> Line 396 is:
> ns_free(config);
>


--
Freddie  Mendoza
[EMAIL PROTECTED]


--
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.

Reply via email to