|
![](/i/fill.gif) |
Warp wrote:
> That was a relatively common problem in C and C++ years ago, but nowadays
> especially C++ compilers have got much better at debugging such things.
How does it handle uninitialized variables? Data flow analysis? That's often
where I find heisenbugs come from, more than random walks off the ends of
arrays. That, or accessing memory that has already been freed.
Me, right now, I'd be happy not spending 3 days trying to figure out what to
change such that the program that gets downloaded during 'make' that
generates the makefile it later invokes whose every compilation line is 100%
macros most nested at least 5 deep in definitions no longer tries to strip
the symbols off a library that's actually a text file, with the comment
"just in case" printed out above it.
--
Darren New, San Diego CA, USA (PST)
"We'd like you to back-port all the changes in 2.0
back to version 1.0."
"We've done that already. We call it 2.0."
Post a reply to this message
|
![](/i/fill.gif) |