How to auto insert logs when use gcc compile a C/C++ source.

How to auto insert logs when use gcc compile a C/C++ source.

[Mr. Joey]

hi,  guys
     
How to auto insert logs when use gcc compile a C/C++ source. I thinks it’s useful when quickly debug a crash.

Thanks

Re: How to auto insert logs when use gcc compile a C/C++ source.

[Xi Ruoyao]

On Mon, 2022-05-30 at 08:45 +0800, Mr. Joey via Gcc-help wrote:
> hi,  guys
>      
> How to auto insert logs when use gcc compile a C/C++ source. I thinks
> it’s useful when quickly debug a crash.

I don't understand your intention.  You mean debug a crash in GCC itself
("Internal Compiler Error") or a crash of the executable created by GCC?

For the prior, the output of -fdump-tree-* and -fdump-rtl-* can serve as
a log.  But it's more efficient to just minimize the testcase with a
tool like cvise and debug the compiler with GDB.

For the latter, it's impossible.  You can use a logging library like
boost::log in your program anyway.


-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

Re: How to auto insert logs when use gcc compile a C/C++ source.

[Mr. Joey]

Thanks Ruoyao
     
        I means later, trace a program created by gcc.

        As I know there is finstrument-functions options,  is this feature I can use to insert a log to trace program run flow?

  



Sent from my iPhone

> On May 30, 2022, at 6:40 PM, Xi Ruoyao <xry111@xry111.site> wrote:
> 
> Xi Ruoyao