diff options
Diffstat (limited to 'public/java-segfault.md')
| -rw-r--r-- | public/java-segfault.md | 16 |
1 files changed, 10 insertions, 6 deletions
diff --git a/public/java-segfault.md b/public/java-segfault.md index 0801d60..295ef48 100644 --- a/public/java-segfault.md +++ b/public/java-segfault.md @@ -4,6 +4,10 @@ My favorite bug: segfaults in Java date: "2014-01-13" --- +> Update: Two years later, I wrote a more detailed version of this +> article: +> [My favorite bug: segfaults in Java (redux)](./java-segfault-redux.html). + I've told this story orally a number of times, but realized that I have never written it down. This is my favorite bug story; it might not be my hardest bug, but it is the one I most like to tell. @@ -18,12 +22,12 @@ robot that sometimes runs autonomously, and sometimes is controlled over WiFi from a person at a laptop running stock "driver station" software and modifiable "dashboard" software. -That year, we mostly used the dashboard software to allow the monitor -sensors on the robot, one of them being a video feed from a web-cam -mounted on it. This was really easy because the new standard -dashboard program had a click-and drag interface to add stock widgets; -you just had to make sure the code on the robot was actually sending -the data. +That year, we mostly used the dashboard software to allow the human +driver and operator to monitor sensors on the robot, one of them being +a video feed from a web-cam mounted on it. This was really easy +because the new standard dashboard program had a click-and drag +interface to add stock widgets; you just had to make sure the code on +the robot was actually sending the data. That's great, until when debugging things, the dashboard would suddenly vanish. If it was run manually from a terminal (instead of |