From: Geert Vancompernolle <gvcompernolle@scarlet.be>
To: Insight Forum <insight@sourceware.org>
Subject: Re: Difference between Insight on Linux and Insight on PC?
Date: Sat, 10 May 2008 16:46:00 -0000 [thread overview]
Message-ID: <4825D164.1020708@scarlet.be> (raw)
In-Reply-To: <4825856B.100@gmail.com>
Geert Vancompernolle wrote:
> Hi,
>
> I've been able to compile Insight for PC (next to Insight for Linux,
> which I'm using already for over a year). I'm also able to connect to
> my target, but what I'm missing, is the high level language.
>
> I only see assembler instructions.
>
> I'm using the same executable to debug on Insight for PC, as the one
> I'm using on Insight for Linux. And on Linux, everything is just fine.
>
> My compilation happens on Linux and the location is mapped using
> Samba, on a Windows drive letter. On Linux, the sources are located
> in /home/geertvc/data/homeautomation. On Windows, /home/geertvc is
> substituted on the Z: drive letter.
>
> So, I think the debug information will contain the path to my Linux
> location (being /home/...), while Insight for PC is looking via the
> mapped file (Z: in my case).
>
> If the above is indeed correct, does there exist a kind of "alias", to
> replace /home/geertvc with Z:/???
>
> I think that would solve my problem...
>
> Anyone any idea?
>
Found this one myself... ;-)
To solve my problem, I have to execute the command "set substitute-path
/home/geertvc z:/" in the command window (maybe I can do this
automatically each time I start Insight???).
Once this is done, all references to "/home/geertvc" will be "detoured"
to "Z:/", exactly what I want.
--
Best rgds,
-- Geert
next prev parent reply other threads:[~2008-05-10 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 11:22 Geert Vancompernolle
2008-05-10 16:46 ` Geert Vancompernolle [this message]
2008-05-10 17:05 ` Dave Korn
2008-05-11 5:04 ` Geert Vancompernolle
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=4825D164.1020708@scarlet.be \
--to=gvcompernolle@scarlet.be \
--cc=insight@sourceware.org \
/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).