public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: luberzz@virgilio.it
To: insight@sources.redhat.com
Subject: insight
Date: Wed, 04 Dec 2002 06:53:00 -0000	[thread overview]
Message-ID: <3DDAF87100020C03@ims1d.cp.tin.it> (raw)

I'm using Insight 5.0 on win2000 and cygwin
Insight has a target = i586-wrs-vxworks
All work fine in a console window(break , watch , step) , but when i try

to use View Function Browser i have the message

couldn't stat "/cygdrive/c/pp/myfunction.c": no such file or directory
    while executing
"file mtime $f"
    (object "::.browserwin0.browserwin.hidden.src" method "::SrcTextWin::_mtime_changed"
body line 7)
    invoked from within
"_mtime_changed $filename"
    (object "::.browserwin0.browserwin.hidden.src" method "::SrcTextWin::FillSource"
body line 10)
    invoked from within
"FillSource t $tagname $filename $funcname $line $addr $pc_addr $lib"
    ("SOURCE" arm line 2)
    invoked from within
"switch $current(mode) {
    SOURCE {
      FillSource t $tagname $filename $funcname $line $addr $pc_addr $lib
    }
    ASSEMBLY {
      FillAssembly..."
    (object "::.browserwin0.browserwin.hidden.src" method "::SrcTextWin::location"
body line 26)
    invoked from within
"$itk_component(view_src) location BROWSE_TAG $name $funcname  $line $addr
$pc_addr lib"
    (object "::.browserwin0.browserwin" method "::BrowserWin::_fill_source"
body line 30)
    invoked from within
"_fill_source $f 0"
    (object "::.browserwin0.browserwin" method "::BrowserWin::_toggle_more"
body line 63)
    invoked from within
"::.browserwin0.browserwin _toggle_more"
    (in namespace inscope "::BrowserWin" script line 1)
    invoked from within
"namespace inscope ::BrowserWin {::.browserwin0.browserwin _toggle_more}"
    invoked from within
".browserwin0.browserwin.view.visible.btn invoke"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke]"
    (procedure "tkButtonUp" line 8)
    invoked from within
"tkButtonUp .browserwin0.browserwin.view.visible.btn"
    (command bound to event)errorCode is POSIX ENOENT {no such file or directory}

Best Regards
Lucaino Bertazzoli


             reply	other threads:[~2002-12-04 14:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04  6:53 luberzz [this message]
2002-12-04  7:06 ` insight Keith Seitz
  -- strict thread matches above, loose matches on Subject: below --
2019-01-10  9:58 insight malaoba
2019-01-16 19:40 ` insight Keith Seitz
2019-01-17 10:55   ` insight Andrew Burgess
2004-01-07  5:17 insight Himansu Doshi
2004-01-21 14:51 ` insight Keith Seitz
2003-02-09  3:07 Insight vk
2003-02-10 13:14 ` Insight Fernando Nasser
2000-03-28 20:50 insight Reed Kotler (Reed Kotler Systems Inc)
2000-03-28 20:54 ` insight Mo DeJong
2000-03-28 21:02 ` insight Andrew Cagney
2000-03-23  8:00 insight Michael J. Carmody
2000-02-09  0:13 Insight Olivier Saudan
2000-02-09 11:05 ` Insight James Ingham
2000-02-03 16:42 insight andy
2000-02-03 16:46 ` insight Mo DeJong
2000-02-03 18:26   ` insight Brendan J Simon
2000-02-03 18:53 ` insight James Ingham
2000-01-13 14:54 Insight Miller, Rob
2000-01-16 20:02 ` Insight Brendan J Simon

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=3DDAF87100020C03@ims1d.cp.tin.it \
    --to=luberzz@virgilio.it \
    --cc=insight@sources.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).