Re: About machine.md in Insight Gdb in GCC porting

[Keith Seitz <keiths@redhat.com>]

daniel tian wrote:

> I didn't used the normal gdb command mode. I just type the Insight
> command, and run it, then open my cc1 file.

Change of tack: whenever you get somewhere you expect to see you .md 
file, open the console window and type "list". What does that say?
Also, can you tell me what you do to reproduce the problem?

If you give me a target triple and a test procedure, I can try to 
reproduce a working case here and use that to troubleshoot your 
scenario. Did you say some variety of arm worked?

> Here is my compiling command:
> 
> export CFLAGS='-gdwarf-2 -g3'
> export LIBCFLAGS='-gdwarf-2 -g3'
> export BOOT_CFLAGS='-gdwarf-2 -g3'

You should not need to specify -gdwarf-2 and -g3 (that I know). On most 
targets, -g will default to outputting dwarf 2. Just to eliminate the 
possibility (and I'm not saying that specifying both will do anything 
wrong), try just using "-g" -- at least while we try to debug this.

> I have to say the md file is not a pure C file.

That should not matter as long as the compiler (and assembler, if 
assembly is involved) are outputting debug info. I suspect they are not, 
but again, I don't know anything about gcc .md files or how they are used.

Keith