Question Segmentation fault

We talked about this on TBA. But maybe someone else can give a more definitive answer. JTP is using cygwin so I think the shutdown command doesn't work properly on Windows. I don't think it is a bug, just Cygwins inability to emulate Unix on Windows.

The shutdown might be because i use cygwin, but the same thing GDB says i also get online in syslog when someone uses whirlwind

Oh aparently i ended gdb wrong, not qhen i quit it right i get the following message about there the problem is:

0x004e21ae in next_in_list (pIterator=0x6105d0) at lists.c:196
196 pContent = pIterator->pItem ? pIterator->pItem->pContent : NULL;

what does this mean ??

I have same issues with a stock tba 3.64 have tried same using stock tba 3.63 with no issues

I started looking at the clean up code in comm.c that runs after the main game loop. (lines 359 to 385)
Added a log("xxx"); before and after each of the free_xxx to try and figure out which one was causing the segmentation error and I could not re-create the error.

Removed the added code and error is back. Started commenting out each of the lines and again crash vanishes.

Just added curly brackets on the if statement on line 379 and also the crash has gone

Operating System?
Current Revision?
MUD Client?
GDB Output?

I tried to duplicate the color issue, the crashing issue, and the group issue with no success so I'll need some more info if I'm going to contribute to a solution.

My GDB Says:
WARNING: Attempting to merge iterator to empty list.
WARNING: Attempting to remove irerator from NULL list.
WARNING: Attempting to remove contents that don't exist in list

Im on Windows
Tbamud 3.64
Using Gmud