Debugging C code after preprocessor?

[Larry W. Virden]

I am looking for comments/suggestions/alternatives as to how to handle
the following problem.

In my work environment, there are several 'preprocessors' that are used.
For instance, lex, yacc, m4, an inhouse c language preprocessor, and
objective-c, as well as ATT C++ in some versions all qualify as the
type of preprocessors that I am talking about.

The problem though is getting this code into a debugger.  We are using
Ultrix and SunOS, and dbx tends to have problems with preprocessed
code.  Lines either dont correspond well, or the user really has a problem
figuring out where in the original code the debugger is.

Anyone have any ideas, or alternatives, which would make working in such
an environment easier?

How about tools like Sabre-C - do they handle external preprocessors 
'properly' (whatever THAT means!)?