Toolset/Nwserver crashes when closed with particular module

[Legacy_Shadooow]

               Both my toolset and nwserver crashes when I close them with my module. I guess it must be somewhere in haks, but I had no clue to where to look. I use CEP1 with 2das updated to 1.69 and then special lite version of PRC with 10 prcs, some feats and spells mostly. Then some stuff like DOA baseitems...

Well what could cause this exactly? I can't find any problem in 2das etc...
               
               

               
            

[Legacy_Shadooow]

               thread resurrecting, still didn't found the cause (as I had other projects), but its quite critical issues as because the error message NWNX cant restart the server properly.

Anyone have idea?
               
               

               
            

[Legacy_kalbaern]

               Are you running the toolset from the same computer that you use to host and while hosting?
               
               

               
            

[Legacy_Shadooow]

               nope, two different computers, crashes with this exact module (not any other module) - thus I suspect its in haks as module itself shouldnt be cause, but not sure how to find the exact issue in haks
               
               

               
            

[Legacy_henesua]

               Well first I would create a new module with the exact same hak setup, but no scripts, and see if the problem persists in the new module as well.

Then if it is due to the haks you can try to isolate which hak is causing the problem.

This could however be caused by other resources right?
               
               

               

                     Modifié par henesua, 28 novembre 2011 - 04:26 .
                     
                  

            

[Legacy_Lightfoot8]

               What is the error you get?
               
               

               
            

[Legacy_Shadooow]

               

henesua wrote...

Well first I would create a new module with the exact same hak setup, but no scripts, and see if the problem persists in the new module as well.

Then if it is due to the haks you can try to isolate which hak is causing the problem.

This could however be caused by other resources right?

Good idea, Ill try it.

Lightfoot8 wrote...

What is the error you get?

classical windows "application attempted to perform permitted operation and must be terminated" or something like that I have windows in my native language...
               
               

               
            

[Legacy_Shadooow]

               

henesua wrote...

Well first I would create a new module with the exact same hak setup, but no scripts, and see if the problem persists in the new module as well.

Then if it is due to the haks you can try to isolate which hak is causing the problem.

This could however be caused by other resources right?

So its in my konfig hak. I somehow suspected this as its the only one my custom hak with 2das. Now I guess I will have to try to add 2DAs one by one to get the one... Not really fun with 70 2DAs (and I already exluded another hundred class related ones)
               
               

               
            

[Legacy_Lightfoot8]

               

ShaDoOoW wrote...



classical windows "application attempted to perform permitted operation and must be terminated" or something like that I have windows in my native language...

Twords the bottom of that window there should be a line that says something like. 

" To see what the error report contains."  

then a link right after it.   Clicking the link should give something like:

 siginfo: ExceptionCode=0xc0000096
Registers:
EAX=0x00880238, EBX=0x00000001, ECX=0x050e2eb0, EDX=0x6d103af8
ESP=0x033ef9fc, EBP=0x033efa2c, ESI=0x0306d928, EDI=0x00000001
EIP=0x050e2ebf, EFLAGS=0x00010a82
 
Top of Stack: (sp=0x033ef9fc)
0x033ef9fc:   01050e30 6d09cb4f 033efa94 6d09c650
0x033efa0c:   00000000 00000000 00000001 0306d928
0x033efa1c:   033efa04 033efab0 6d0c04a8 00000001
0x033efa2c:   033efa58 7e418734 00010400 00009819
0x033efa3c:   050e2eb0 00000001 6d09c650 dcbaabcd
0x033efa4c:   00000000 033efa94 6d09c650 033efac0
0x033efa5c:   7e418816 6d09c650 00010400 00009819
0x033efa6c:   050e2eb0 00000001 033efb54 033efb4c
 
Instructions: (pc=0x050e2ebf)
0x050e2e9f:   00 e8 24 02 05 00 00 00 00 18 00 03 00 4f 00 08
0x050e2eaf:   03 38 02 88 00 68 30 0e 05 01 00 00 00 00 76 0c
0x050e2ebf:   6d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x050e2ecf:   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Knowing what the regesters and Top of stack is could help in figuring out the problem.
               
               

               
            

[Legacy_Shadooow]

               "AppName: nwserver.exe    AppVer: 1.6.9.0    ModName: nwserver.exe
ModVer: 1.6.9.0    Offset: 0001ee4b"

thats what it gives, there is also potion for more detailed bug report but that cannot be copied + it contains all dlls etc.

Anyway I already found the 2DA or rather 2DAs that causing this, its custom itemproperty, but so far I wasn't able to fix it or tell what exactly is wrong there.

EDIT: fixed, seems that iprp_costtable must NOT have any empty line or invalid reference

[SOLVED]
               
               

               

                     Modifié par ShaDoOoW, 28 novembre 2011 - 07:53 .
                     
                  

            

[Legacy_Lightfoot8]

               Sounds about right.   The 0001ee4b  offst was  where the location of an object was being loaded to be cleaned and removed from the heap.   So it was looking for something that was not there.