On Wed, 27 Mar 2019 at 14:31, William Tambe wrote: > > yes, it happen every time; I am doing porting work using gcc-8.2.0. so > it is probably something I am missing, and I was wondering how to go > about debugging it. Ah there's a whole wiki page on that topic: https://gcc.gnu.org/wiki/DebuggingGCC tl;dr build an unoptimized gcc with debuginfo, then run it under a debugger.
