Question Segmentation fault

Hi

When i wanna shutdown the mud i type shutdown die
but then in shell i get this:
$ ./autorun: line 174: 3452 Segmentation fault (core dumped) nohup bin/circle $FLAGS @PORT >> syslog 2>1

in the lib folder i see a circle.exe.stackdump file

anyone who can tell me how to GDB it or know what this problem is about ?


when i edit the stackdump it shows:
Exception: STATUS_ACCESS_VIOLATION at eip=004EDFAE
eax=00000000 ebx=80048750 ecx=80048750 edx=009F0812 esi=000015B3 edi=00000003
ebp=0028AB98 esp=0028AB80 program=C:\cygwin\home\JTP\tbamud364\tbamud-3.64\bin\circle.exe, pid 3776, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
0028AB98 004EDFAE (00598870, 00000003, 0028ABC8, 004EE0EB)
0028ABC8 004EE19C (80048750, 80048750, 0028ABE8, 00451083)
0028ABE8 004EE238 (80048750, 00000005, 00000000, 0028AC48)
0028AC68 004ED9DD (00000003, 0028AC90, 80010100, 6127590C)
0028ACF8 6100763A (00000000, 0028CD78, 61006C50, 00000000)
End of stack trace

Have you read this tutorial JTP?

tbamud.com/forum/4-development/6-debugging-tutorial-for-gdb

Yes typing that says there is no such file

You'll need to run your mud _through_ the debugger instead (since windows doesn't generate core dumps).

To do this, first verify that you can create the segfault outside autorun by running "bin/circle", triggering the crash and verifying that you get segfault in the log.

Now run gdb with this command:
gdb bin/circle

and in the gdb prompt, type "run".

Note that the gdb version will run somewhat slower as gdb adds some checks for every command.

When you now trigger the crash, the gdb process will stop the program from exiting, and you can use the same procedure as mentioned in the post above.

Running GDB
it shows this when i shutdown:

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.



Thats all

When a player uses whirlwind i also get 6 lines of warning about iterator, but they come in SYSLOG online.


Someone pls tell me what this is about.

We will have to ask Vatiken about this one...

On the same note (since upgrading to 3.64) I have noticed sometimes when forming groups that the warnings about the lists appear. I will try to note it next time it happens so I can report better detail about the possible issue.