zero pain (finding the function in C)

The ‘Sherlock’ module has morphed into something more than mere symbolic disassembly etc, it now has the ability to produce state/memory dumps when an exception occurs, and then to redirect its normal *commands to a reloaded image of that failure on the developer’s machine, to – hopefully – work out what happened. It is close also to acquiring support for ASD in builds that include that, and thus providing source-level information on where a failure occurred.

My aim is to build something that will help other developers/maintainers; so, please, do you have any suggestions/ideas how it can be improved?

Sorry that I’m late to this thread!

A method that I often use to find bugs in my code when calling (say) strcmp() would be to do something like this:

In a header file:

#define strcmp(a,b) debug_strcmp(a,b,__FILE__,__LINE__)
extern int debug_strcmp (const char *a, const char *b, const char * filename, unsigned int linenum);

Then in a handy place:

#undef strcmp
int debug_strcmp (const char *a, const char *b, const char * filename, unsigned int linenum)
{
  if (a == NULL)
  {
    printf ("a = NULL called from %s line %u\n", filename, linenum);
    return (1);
  }
  if (b == NULL)
  {
    printf ("b = NULL called from %s line %u\n", filename, linenum);
    return (1);
  }
  return (strcmp (a,b));
}

(Sorry about the bad formatting, bloody textile!)

Umm… assert() ?

Doesn’t help as the assert gives the file/line where the assert is, not the caller.

The original problem was to find which of many calls to strcmp was the culprit.
By replacing the original call (strcmp, or anything else) with an alternative that
range checks the params and can be replaced when part of an ‘if’ statement.