UnhandledException hooking?

[Baaleos]

Im using nwnx_funcs, nwnx_areas (both of which are revisions by Maxrock) heavily in my module, but im noticing frequent crashing, but I cant seem to put my finger on the cause of the crashes.


I was wondering if its at all possible to hook onto Exceptions in nwserver.exe and find out what script was running, to cause the exception?

All I get at the minute, is
1. Server running fine,
2. I go away for dinner,
3. Come back 30 minutes later
4. Find nwnx restarted a locked up server, and there is still a Microsoft error report msg box on screen, saying that an error occured in nwserver.exe.


Unfortunately, the logs arent that useful, because while they are set to level 3 etc or the max setting, they dont tend to keep track of the time or date of the function calls.

And even more annoyingly, because nwnx kept running dispite of the crash, the logs just get appended onto eachother seamlessly, meaning its impossible to tell where the crash occured in the nwnx funcs log file.


Can anyone suggest possible diagnostic methods to finding causes of crashes?

Im about to start putting in Debug Messages at the start of all the functions I suspect are causing crashes.

Eg

[Baaleos]

Anyway.... I think this may have belonged in the tech support,
but the question stands.

Does anyone thing its possible to create a nwnx plugin, which could actually get more detailed explanations of exceptions caused in nwn?


Eg - In C# you can use a try and catch statement to display error boxes with the cause of the crash, and sometimes the name of the function.

Is anything like that possible here?

Or,
If I take note of the Offset of the error, am I able to look this up in IDA to get a better idea of what function crashed?

[Baaleos]

Offset:0000b876

But the cause of the error is still a mystery to me...

[MaxRock]

CExoString::CExoString is one of the constructors for the string class.
And a crash at that point actually looks familiar...

There is a problem with destroying areas in which characters have logged out; although I thought I had fixed that...

try adding this to nwnx.ini

[Baaleos]

One of my players was just saying to me, that the server seemed to crash just as I had logged out.



I purposely designed our 'Spectral Realm' system to destroy the spectral copies of areas, when the Material Realm version of that area was also empty.

To prevent a player from transitioning into the spectral realm, as it is being destroyed (a player did this, then ended up in limbo - BLACK).

Eg - if they are in the material realm original of the spectral realm copy, then there exists the possibility of them transitioning into the spectral realm in one transition or less.
So I decided to keep the spectral realm around, and keep checking to see if the material realm original becomes empty, and when it does, then it safely deletes itself.

Clearly it didnt seem to want to do this.

So, just to clarify,
You want me to put this
SetLocalLocation(GetModule(), "LocationFailSafe", GetStartingLocation());

in the onClient Exit code of the module?

Oh... theres something I never thought about...
What if a player logs out inside the Spectral Realm.... darn...
Im gonna have to script it so that onClientExit, it determines if its in the spectral realm. Lol
This is a video of the spectral realm, you have heard so much about in this post. It is reliant on the nwnx_areas plugin.
http://www.youtube.com/watch?v=uLX5jpTYSGg

[Baaleos]

just re-read that.

So set the failsafe, on the onModLoad event?

[Baaleos]

nwnx_funcs isnt building.

Think you forgot to include

[MaxRock]

Ack, you're right, I didn't commit the classes and includes. Should be there now.

Edit:

[Baaleos]

k, its terrible when im right isnt it. Lol

I also confirmed my fears that players can cause crashes, if they leave an area via disconnect, area is destroyed, then they rejoin in that erased area.

The error occurs in
offset 123161 - the CNWSTile:GetLocation() function.

I guess im gonna have to be more creative about my approach to destroying areas, or determining when is safe to destroy areas.

The only problem, is that there is no way to differentiate between leaving the area, and leaving the module, since leaving the module, calls the areaLeave event too.

Leaving the Area = Good, Can delete
Leaving the Module = Bad, should keep the area just incase.


Alternativly, if it were possible to resend the player to StartLocation in the event his area doesnt exist.

This cant be done with simple nwnscript, since GetLocation gets called before nwnscript can be called.

[Baaleos]

Anyway, I just did a test of the FailSafeLocation set, and no apparent crashes, but that being said, It was just me in the server at this time.


Tomorrow I will get a few people in, and see if we can cause some crashes.

Note - The nwnx_funcs.dll builds fine now.

Is there an nss with it -..... found it.

NWNXFuncs_ClearPlayerTURDs() Looks like it might fix my problems, to a degree - it would prevent players from reappearing in areas that dont exist, but its a pitty that its a global / all player affecting function.

Is it possible to access the stored data, such as player locations etc stored on the server?

Would it be possible to change this data, after the player is gone?