public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Syd Polk <spolk@redhat.com>
To: "Dennis K. Peters" <dpeters@engr.mun.ca>
Cc: insight@sourceware.cygnus.com
Subject: Re: Insight 5.0 on Linux
Date: Mon, 08 Jan 2001 09:36:00 -0000	[thread overview]
Message-ID: <3A59F9C2.8B781594@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.20.0101081028400.31392-100000@delphi.engr.mun.ca>

"Dennis K. Peters" wrote:
> 
> Hi Insight team,
> 
> I have two questions, both of which are probably FAQ, but I couldn't find
> an FAQ on your web site so I've got to ask them.
> 
> 1) I'm trying to upgrade my existing Linux (Slackware 7.0) system to use
> Insight 5.0. It seems that the distribution comes with a bunch of stuff
> that I already have and in some cases have more recent versions of (e.g. I
> have tcl 8.0.5 installed, the distribution comes with tcl 8.0.4). I'm
> reluctant to install over these existing versions, particularly if it
> means going backwards in version numbers, so I'd like to use what I've
> already got, but the confgure/make doesn't seem to use what I have. Is
> there an easy way to just build and install the new gdb executable (and
> corresponding documentation etc.), and be informed if I'm missing anything
> else. (Isn't this the way configure usually works?)
> 


Insight requires the version of tcl/tk that it uses. It is happy to
co-exist with an existing installation; you should build it with

./configure --prefix=/usr/redhat/insight

and put /usr/redhat/insight/bin in your path.

This also has the nice effect that you won't overwrite the gdb version
that comes with RH.

> 2) Having built successfully, but not installed, I've tested it in my the
> build directory. It seems to work fine if I start it in a (bash) shell in
> the foreground, but if I background the process (i.e., "gdb <file> &"),
> when I click the 'run' icon it loops forever. (The first statement in the
> program I'm debugging is of the form 'cout << "This program ...', if that's
> important.)

Insight will not work if executed in background. It is really hard to
get it to work that way, as every different operating system has really
bizarre ways to do pseudo-terminals.
 
> Thanks in advance for your assistance.
> 
> Dennis Peters
> 
> Dennis K. Peters, Ph.D., P.Eng.            | dpeters@engr.mun.ca
> Faculty of Engineering & Applied Science   | http://www.engr.mun.ca/~dpeters
> Memorial University of Newfoundland        | Ph: (709) 737-8929
> St. John's, NF  Canada  A1B 3X5            | Fax: (709) 737-4042

  parent reply	other threads:[~2001-01-08  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08  6:18 Dennis K. Peters
2001-01-08  7:17 ` Fernando Nasser
2001-01-08  9:36 ` Syd Polk [this message]
2001-01-08 15:02   ` Tom Tromey

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=3A59F9C2.8B781594@redhat.com \
    --to=spolk@redhat.com \
    --cc=dpeters@engr.mun.ca \
    --cc=insight@sourceware.cygnus.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).