Let's say that double-clicking on Poker Copilot's "Position Summary" screen crashes Poker Copilot one time in 100. To find this bug, I'd have to use the screen a lot. Many times to cause the bug, and many times more to reproduce the bug. But if 100 people used the Position Summary screen in one day, chances are that the bug would rear its head at least once most days.
To help track down some obscure issues like this, I added a Crash Reporter to Poker Copilot 2 a couple of weeks ago. If Poker Copilot crashes, the Crash Reporter springs to life, notifying the user, and offering them a chance to send the crash report to Poker Copilot international headquarters. Location: my home office.
The crash report sends the error message plus a snapshot of the state of Poker Copilot. (For the techies: a stack trace and thread dump, plus assorted system properties.)
I'm now getting several crash reports a day, and lordy me, are they ever helpful. That hypothetical once-in-a-100-times bug I described above? It wasn't hypothetical at all. It was very real, and with the help of crash reports I mercilessly murdered it.
Thursday, 11 June 2009
Poker Copilot's Crash Reporter
Subscribe to:
Post Comments (Atom)
Poker Copilot Translation Project
Want to use Poker Copilot in your language? Then help with the Poker Copilot Translation Project.
Blog Archive
-
▼
2009
(337)
-
▼
June
(29)
- Poker Copilot: One Year Old
- Poker Copilot 2 Early Access Program Update
- Poker Copilot 1.76 Released
- A Lousy Poker Copilot Week - And a New Feature
- Stuff from Aidan + Posterous = Instant New Blog
- Food, Inc
- Poker Copilot HUD always on?
- Sub-Millisecond Query Optimisation
- Poker Copilot 2 Early Access Program Update
- Multi-table HUD demo
- What's Poker Copilot Missing that Hold'em Manager ...
- Finding Memory Leaks in Cocoa + Objective-C
- FastSpring and Credit Card Fraud
- Does Poker Copilot have Ongame Network Support?
- Poker Copilot 2 Early Access Program Update
- Poker Copilot Tutorial in French
- Mac-ify your Full Tilt Poker
- Why does Poker Copilot talk to the Internet?
- Poker Copilot's Crash Reporter
- Sentence of the Day
- What I've Been Reading
- Obscure Sentence of the Day
- Cha-ching!
- Statistic of the Day
- Hero Stats for Current Table Only
- Poker Copilot 1.74 Released
- C is to Java as Java is to what?
- Competitors for Google?
- Poker Copilot goes Cyrillic?
-
▼
June
(29)

8 comments:
My little snitch
http://www.obdev.at/products/littlesnitch/index.html
shows me a couple different place PC connects to. maybe one day you could go into some detail.
The Crash Reporter - the only feature of copilot 2 I am actually able to use. ;(
"The Crash Reporter - the only feature of copilot 2 I am actually able to use. ;("
Haha! Mine crashes as soon as I turn on the HUD. It looks great though and I can't wait to get a working version.
Steve, any plans to support HORSE? PCP is completely befuddled by PStars cash and tourney HORSE games. I can send some HHs if it will help.
Did you use a 3rd party framework for this, or did you roll your own?
I rolled my own crash reporter.
No plans to support HORSE yet...
Could you provide any tips on how you wrote your crash reporter? Does it just send stack traces to you, or is there more information from key data structures?
@Orthene
If you know something about Java, here's what we send:
* Thread.getAllStackTraces()
* System.getProperties()
* Some additional Poker Copilot specific properties, such as version and hand history folders
Thanks! I had never run into that method, that'll be a big help.
Post a Comment