From: daniel tian <daniel.xntian@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: About machine.md in Insight Gdb in GCC porting
Date: Tue, 07 Jul 2009 09:38:00 -0000 [thread overview]
Message-ID: <121fadb80907070238k2291724bu9c2434f3c9a93d57@mail.gmail.com> (raw)
In-Reply-To: <4A52B7A1.1080104@redhat.com>
Hi:
>
> 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?
>
I have tried in both GDB and Insight, the md file doesn't appear. The
list you mentioned is at left-top of the Insight GUI?
There is no such file in that list.
I don't know what 's the "a target triple " mean. Sorry.
> 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.
>
You solution seems to make sense, but I 've already tried your
solution to remove the -gdwarf-2 and -g3 flag.
And the md file still does not appear in Insight.
>
> 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.
>
There is no assembler. it compile the c language to my machine assemble.
MD file is compounded with RTL (GCC intermediate language), which used
to describe machine instruction pattern, and C language.
HiThanks.
prev parent reply other threads:[~2009-07-07 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <121fadb80906291848y61466ae6yd167e6a03321d9fa@mail.gmail.com>
2009-07-06 22:04 ` Keith Seitz
2009-07-07 2:04 ` daniel tian
2009-07-07 2:10 ` Keith Seitz
2009-07-07 2:39 ` daniel tian
2009-07-07 2:49 ` Keith Seitz
2009-07-07 9:38 ` daniel tian [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=121fadb80907070238k2291724bu9c2434f3c9a93d57@mail.gmail.com \
--to=daniel.xntian@gmail.com \
--cc=insight@sourceware.org \
--cc=keiths@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).