??? 03/08/04 19:14 Read: times |
#66279 - RE: Not-so-mysterious errors Responding to: ???'s previous message |
Nope. This is the beginning of generic Windows BSOD.
Erik... Allowing buffer overruns IS a programmer's error. If you use a string that is not null-terminated... If your specifier wants more variables than required... If you request a pointer but provide a variable... If your variable types don't match the specifier... these are all programmer's errors. Printf() is a heavyweight tool, like a motor chainsaw, you can cut down a tree, but you can't sharpen a pencil. You can easily cut your hand off too, and then you should only blame yourself for that, not makers of the chainsaw. |
Topic | Author | Date |
An Error in Kiel | 01/01/70 00:00 | |
RE: An Error in Kiel | 01/01/70 00:00 | |
Keil | 01/01/70 00:00 | |
RE: An Error in Kiel | 01/01/70 00:00 | |
RE: An Error in Kiel | 01/01/70 00:00 | |
Some mysterious errors | 01/01/70 00:00 | |
RE: Some mysterious errors | 01/01/70 00:00 | |
RE: Some mysterious errors | 01/01/70 00:00 | |
RE: addendum to the above | 01/01/70 00:00 | |
Not-so-mysterious errors | 01/01/70 00:00 | |
RE: Not-so-mysterious errors | 01/01/70 00:00 | |
RE: Not-so-mysterious errors | 01/01/70 00:00 | |
RE: Not-so-mysterious errors | 01/01/70 00:00 | |
RE: Not-so-mysterious errors | 01/01/70 00:00 | |
RE:printf![]() | 01/01/70 00:00 | |
RE: An Error in Kiel | 01/01/70 00:00 | |
LX51: How will that help? | 01/01/70 00:00 |