Good points - maybe "arcane" would have been a better word to describe WinDbg - you can do just about anything, provided you know the right incantation. I hope you enjoy ForensicDbg!
I always thought that traffic signals should be trying to minimize squared anger, where anger increases linearly with time spent waiting at intersection.
one thing that drives me nuts is a left turn arrow that isn't long enough to clear all the cars waiting in the left turn lane. So often, it would only need another 5-10 seconds but it seems to have a limit that it can't exceed. This leads to frustrated drivers trying to squeeze through on the yellow light or even the red.
Also red left turn signals should not be a thing. If there's a gap in the oncoming traffic you should be allowed to turn left across it as long as the straight-ahead traffic has a green light.
Where I live (in the PNW) they mostly are not a thing any more. The only ones remaining are there because the combination of sight line and traffic speed makes them too dangerous to turn into flashing yellow. Not sure if that has spread to other regions, but I would guess it is heading towards being universal pretty quickly.
The only possible second-or-third order effect of red cross-traffic arrows is to decrease the downstream traffic on the cross road. Mostly, the places where I encounter them have a low traffic cross road. IMHO, in those situations, red cross-traffic arrows are simply a failed "traffic engineering fad".
(Edited to fix a typo and generalize "red left-arrow" to "red cross-traffic arrow" to account for left-side-of-the-road driving systems.)
I'll grant that it might be safer for pedestrians, as then they only have to watch for right-turning traffic and not people turning left from the opposite side of the road. There are a lot of intersections that rarely see pedestrian traffic though.
1: Don't keep it in memory. If you have to, keep it in memory for as short as time as possible and scrub it afterwards. For example, password fields.
2: If you generate crash dumps, scrub the dumps when you generate them. Some crash reporting services offer to do this automatically.
3: If you are writing anything client/server, where you control the server and the client runs on a users machine, never trust the client. Expect that it has been hacked, is being debugged, and is actively hostile.
This is a great writeup — bookmarking it. ForensicDbg is Windows-only right now, but I could easily see a day where I'm in your exact shoes trying to get a native postmortem debugger running on macOS.
reply