Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

• Issue ID

  #000995

• Severity

  3 - Medium

• Status

  Invalid

• Return to Issue Listing

Issue Confirmations

• Yes (0)No (0)

0

Sig Plugin Defect - Incomplete Stack Trace

Posted by Hercules Bot on 18 February 2008 - 04:41 PM

Originally posted by theultramage
http://www.eathena.w...ker&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.

• Back to top

Hercules Bot

Nov 23 2012 04:43 AM

Originally posted by mkbu95
Plugins were removed.

• Back to top

1. Bug Tracker
2. → Hercules Bug Archives
3. → Core
4. → Severity: Medium
5. → Status: Invalid
6. Privacy Policy
7. Hercules Forum Rules ·