This is the mail archive of the
insight@sourceware.org
mailing list for the Insight project.
Re: About machine.md in Insight Gdb in GCC porting
2009/7/7 Keith Seitz <keiths@redhat.com>:
> daniel tian wrote:
>>
>> But I have already asked in GCC maillist about the same question. They
>> suggested I should send the question in Insight/GCC maillist.
>> I should the same compile flags with MIPS and ARM. But md file will
>> appear when I debug ARM/MIPS cc1 file with insight. My port doesn't.
>> So I wonder there is something I missed.
>
> Does it work with "normal" gdb at all? If not, it must be either a gdb
> problem (gdb cannot locate the file) or a compile time problem (no debug
> info or something).
>
> Can you show me a gdb (command line: insight --i=console) session
> demonstrating the problem? I might be able to help figure out what's gone
> wrong.
>
> Keith
>
I didn't used the normal gdb command mode. I just type the Insight
command, and run it, then open my cc1 file.
Here is my compiling command:
export CFLAGS='-gdwarf-2 -g3'
export LIBCFLAGS='-gdwarf-2 -g3'
export BOOT_CFLAGS='-gdwarf-2 -g3'
mkdir build-rice-gcc
cd build-rice-gcc
../repos-gcc-4.0.2/configure --target=rice --enable-languages=c
--with-dwarf2 --no-libgcc
When target replaced with MIPS/ARM, machine description (*.md) file
will appear. PS, my target is named "rice".
Maybe there is something missed in configure file like config.sub,
config.gcc or makefile. I just don't know how. So maybe your guys met
the same problem before. I have to say the md file is not a pure C
file.
Thanks.
daniel tian