As we know, during the debugging, GDB can expand the macro when a particular GCC option is enabled. But this raw source code is not quite convenient compared to debugging.
If the macro is a tool for the expansion of in-place and is changed to compile the original source code for the GCC, then it would be good
if any such If I do not have the tools, then I will make one and there are some hard ideas for your comments
Using "GCC-A" to compile source code with macro and output As a result of some temporary files, Extending the extended source code and To create the original source code, compare the original source file with some smart def / compare compared to the pre-processed file whose macro is expanded
One idea is to use GCC-A, then edit the .i file as a result and delete the # line instructions around the affected area. Then compile the .i file.
GCC + GDB matrix can be created to debug such as they are inline functions, but I think it would be a fair job in GCC.
No comments:
Post a Comment