That's no good...

Login to Account: ./data/accounts/m/ma/marlonwilliamhunter/marlonwilliamhunter.acc
PLAYER: ./data/players/o/ob/Obliterator/Obliterator.pl
load obj for player: Obliterator
Send new_player(): socket 6
INFO:: Load map >/planes/demon_plane/captured_stronghold/captured_stronghold_a_0003<... INFO:: get_online_players_info was called and all buffers were reset.
INFO:: Load map >/planes/demon_plane/captured_stronghold/captured_stronghold_a_0002<... ==24027== Jump to the invalid address stated on the next line
==24027==    at 0x74753C3E220A3035: ???
==24027==    by 0x2032323A3830223C: ???
==24027==    by 0x41303820332F3830: ???
==24027==    by 0x657551223D622244: ???
==24027==    by 0x6C53206F54207472: ???
==24027==    by 0x6F72462061207960: ???
==24027==    by 0x796D7241206E6579: ???
==24027==    by 0x736F724620303509: ???
==24027==    by 0x27746E6169472073: ???
==24027==    by 0x3A74726165482072: ???
==24027==    by 0x220A30352F36341F: ???
==24027==    by 0x3830223D74753C3D: ???
==24027==  Address 0x74753c3e220a3035 is not stack'd, malloc'd or (recently) free'd
==24027==

SIGSEGV received.
That's not a very descriptive error message but it looks like perhaps something's wrong with the map? It's an enigma... The server crashed three times, were they all connected?

I'll hook you up with logs tomorrow.

IDK why valgrind has started reporting instead of file, func, line. That should happen if the code is compiled with the -g switch, which it should be.

Hm, I wonder... I'll check... Yes it is.

I remember this happened some time ago when the server boxes were upgraded to the then latest Debian and then worked properly when they were upgraded again. So perhaps it is an intermittent Debian bug (or more likely the gcc package has semi-broken code governing the -g switch).

Here's what I suggest for this Dai bug:

1. Later today I'll grab the main account/player files for Ob annd test locally (where valgrind works) -- it's likely a server bug where it gets confused with many quest updates (I think you must have 50+);
2. Meanwhile, don't login to Ob/your account at all;
3. Remove the quest from Daiserv -- a recent Mapserv log says 'Fixed a lot of bugs in the frostbolt quest script. I *think* it's done, so I need to get around to testing it sometime...' so did you?
4. Cross fingers.

I meant did you test it (on test) or was main your first time doing the quest (with the latest fixes)?

Quick update. I set everything up locally. Re reading the 3 crash logs, I don't think it is to do with the     quest. Rather the mobs (most likely their AIs) you were fighting. So which ones were they? All 3 times the same ones on that CS map?

Not been able to reproduce it yet. But I have used your char to fix two other bugs (which I introduced :oops:) in trunk. Where would I find your +3 sling?

The sling because in each of the three crashes you were fighting with your poking device and your sling, so I want to reproduce the circumstances as exactly as possible.

Damn I look handsome in that photo.