Originally posted by [b]theultramage[/b]
http://www.eathena.ws/board/index.php?autocom=bugtracker&showbug=995
There is a bug in the linux/cygwin crashdump plugin 'sig'. I've suspected it for some time, but I've finally got hands-on proof yesterday when a crash produced both a sig-stackdump report and a gdb full backtrace.
The bug is that either sig isn't logging the topmost call stack entry correctly, or addr2line isn't translating it correctly. It always comes out as
CODE
??
??:0
gdb, on the other hand, displays the topmost entry perfectly.