The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
My current project requires half an hour to build (it has to fetch every component from the main customer server over a slow VPN and cross-compile every module + execute a lot of code generators and yocto run) and can't be debugged stepping into code, we can only register terse debug messages and analyze post-mortem.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
If you cannot reproduce it in the debugger, it could be a stack based variable that is getting overwritten (b/c it is somehow being returned). Logging is the ultimate answer.
It should be repeatable... If it is, it is solvable!
it's repeatable, it's just that it's right in the middle of a LALR parser generator table transformation so building the table in such a way as to reproduce it is the trick. That's why i said i'm sticking with the current repro. Finding another one is tricky, not impossible. It's just because of where the bug is and what it is.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.