public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Martin M. Hunt" <hunt@redhat.com>
To: Martin Alley <martin.alley@ntlworld.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: insight won't debug my program
Date: Mon, 29 Sep 2003 08:03:00 -0000	[thread overview]
Message-ID: <1064822588.2357.16.camel@dragon> (raw)
In-Reply-To: <001f01c385d1$8c235250$3300a8c0@martinjfalley.com>

On Sun, 2003-09-28 at 08:02, Martin Alley wrote:
> Hi All,
> 
> I want to debug a program on RedHat 9 (to which I am fairly new).
> I have downloaded, made and installed Insight/gdb5.3 (./configure,
> ./make, ./make install)
> 
> I want to try "debugging" the monop demo C program.
> I have set up the debugger to run monop, and the working directory is
> that of monop.
> 
> The xterm field is set to xterm -e
> When I click debug, an xterm window comes up with the following
> contents:
> "
> xterm: Can't execvp -T: No such file or directory
> [martin@rh9 monop]$
> "
>  
> 
> I get the insight source window, set a breakpoint at the first
> executable line in main, and hit run - insight then hangs. (cursor is
> watch symbol).
> 
> I have left the command to run insight as insight - not changed it to
> gdb in contradiction to the readme instructions with sourcenavigator.
> 
> 
> How do I troubleshoot my problem?

I don't have a copy of 5.3 around, but I don't recall an xterm field,
just a checkbox.  Does Insight work if you don't use xterm?

Can run debug your program with GDB?

-- 
Martin M. Hunt <hunt@redhat.com>
Red Hat Inc.

  reply	other threads:[~2003-09-29  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-28 15:39 Martin Alley
2003-09-29  8:03 ` Martin M. Hunt [this message]
2003-09-29 13:43   ` Martin Alley

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=1064822588.2357.16.camel@dragon \
    --to=hunt@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=martin.alley@ntlworld.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).