Quote:
Originally Posted by wildwizard
No need for those debugging statements when you run it in gdb with full debugging enabled in the compile you get to see all of that anyway. when it bombs out you type in backtrace and it gives you the chain of functions and where they are in each source file.
gdb also lets you see the pointer addresses which is how I picked up on the code not been 64bit compliant, if your keen it's in word.c
I also had a quick look at the current version just to have a quick look and just the download size gives away the complexity of where it has gone since the early 90's
|
Yeah, I probably should make more of an effort learning to use gdb. But platform-to-platform debugger differences are probably the only thing worse for me than editor differences -- and you already know how reluctant I am to deal with that<grin>. Most of my open source stuff tends to be as platform-agnostic as possible anyway, just ansi standard C. So embedded debug statements, that are default off but can be turned on with a command-line switch (or ?query_string attribute, etc, as appropriate), usually work better for me. I can quickly see all the same stuff regardless of platform, and it's way easier to tell complaining users to just run the program with an extra switch and email me all the output.
