Closed GoogleCodeExporter closed 9 years ago
Added unhandled exception filter:
Todo:
- Get log path from currently running app directory, before the exception handler.
- Store symbols for Broodwar, Battle, Standard, and Storm.
- Create log path directory if it does not exist.
- Possibly Cancel/Retry/Continue dialog, where Retry will reproduce the crash so that it can be debugged, Continue will attempt to bypass the crash(undefined behaviour; for example: divide by 0 becomes divide by 1). Let me know if you're against this.
Original comment by AHeinerm
on 11 Oct 2011 at 2:54
Added custom Broodwar symbol loading.
Todo:
- Get log path from currently running app directory, before the exception handler.
- Create log path directory if it does not exist.
- Possibly Cancel/Retry/Continue dialog, where Retry will reproduce the crash so that it can be debugged, Continue will attempt to bypass the crash(undefined behaviour; for example: divide by 0 becomes divide by 1). Let me know if you're against this.
- Print other useful info such as the current map (and map information, only if in a game).
- Save a replay file up to the point of the crash (only if in a game).
Original comment by AHeinerm
on 11 Oct 2011 at 4:56
TODO:
- Change log path to /Starcraft/Errors/
- Create log path DIR if it doesn't exist.
- Save replay file up to crash point (requires planned BWAPI replay system).
The dialog is going out of the scope of BWAPI, useful info is printed already.
Original comment by AHeinerm
on 3 Jul 2012 at 7:37
Original comment by AHeinerm
on 23 Jul 2012 at 3:59
The remaining task is the commands library.
This is currently going on here: https://github.com/RtsAiResearch/bwapi
Over the holidays I will contact them to see where we are with this.
Original comment by AHeinerm
on 13 Dec 2012 at 8:20
Original comment by AHeinerm
on 7 Jan 2013 at 3:54
To do:
- Give the commands library the ability to write information to a stream, then use it instead of the BW-level commands.
- Write our own replay file dumps.
Original comment by AHeinerm
on 17 May 2013 at 9:00
The BWAPI project is slowly undergoing the migration to GitHub. All issues have
been migrated to the GitHub issue tracker located here:
https://github.com/bwapi/bwapi/issues
In order to receive updates on your issue, please head over to the GitHub issue
tracker and subscribe to your issue.
Original comment by AHeinerm
on 15 Apr 2014 at 7:46
Original issue reported on code.google.com by
AHeinerm
on 8 Oct 2011 at 9:06