public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Michael Trensch <mtrensch@googlemail.com>
To: loody <miloody@gmail.com>
Cc: insight@sourceware.org
Subject: Re: cannot see source in source window when compile as mips
Date: Sat, 08 Jan 2011 15:54:00 -0000	[thread overview]
Message-ID: <4D288893.90700@gmail.com> (raw)
In-Reply-To: <AANLkTimDGbnj+=cmvba2W6pC5B4WkH7Dtu4_Op566YDT@mail.gmail.com>

On 08.01.2011 16:40, loody wrote:
> hi:
>
> 2011/1/8 loody <miloody@gmail.com>:
>> Dear all:
>> I download insight6.8.1 and compile it for suitable debugging mips program.
>> But I cannot see the source in source window as the attach pic.
>> have anyone met the same problem before?
>> BTW, if I try to compile insight6.8.1 with gdb7.2, only I need to do
>> is change gdb folder with the new one?
> I change gdb with gdb7.2 and can successfully compile it.
> But I cannot find insight binary in my prefix/bin folder.
>
> it seems it is not enough just replace old gdb folder with the new one.
> Should I have to config something, right.
> BR,
> miloody
I don't know what you will need to change in the source tree.

But the latest cvs should contain GDB 7.2. I am successfully using
insight cvs (2010/12/11) with GCC 4.5.2 (which needs the gdb 7.2) on a
ARM9 platform.

Probably you should give this a try.

Regards,
Michael

  reply	other threads:[~2011-01-08 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimZqizCViN+svHLZemp84T2USo9QQk2_7Bo23Be@mail.gmail.com>
     [not found] ` <AANLkTi=tNf5O3Z7oSJRrCc5dsKBWJ4x=96-TNvSSehKZ@mail.gmail.com>
2011-01-08 15:40   ` loody
2011-01-08 15:54     ` Michael Trensch [this message]
2011-01-09 16:08       ` loody

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=4D288893.90700@gmail.com \
    --to=mtrensch@googlemail.com \
    --cc=insight@sourceware.org \
    --cc=miloody@gmail.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).