public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: kseitz@sources.redhat.com
To: alan@carwiles.com, insight-prs@sources.redhat.com,
	kseitz@sources.redhat.com, nobody@sources.redhat.com
Subject: Re: insight/349: UI hangs using 6.8.1 on Linux (CentOS) and contact info on website is wrong
Date: Thu, 29 Apr 2010 21:11:00 -0000	[thread overview]
Message-ID: <20100429211146.3400.qmail@sourceware.org> (raw)

Synopsis: UI hangs using 6.8.1 on Linux (CentOS) and contact info on website is wrong

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Thu Apr 29 21:11:46 2010
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->feedback
State-Changed-By: kseitz
State-Changed-When: Thu Apr 29 21:11:46 2010
State-Changed-Why:
    1) As far as I know, insight@sources.redhat.com should work. I usually use @sourceware.org, but nonetheless, I will update the web page. [I believe sourceware.org/sources.redhat.com had some problems a day or two ago (failing drive?) and that may be why your message didn't make it through.]
    
    2) Ok, sorry this is so confusing, but... The executables "inisght", "gdb", and "gdbb" are all almost identical. "insight" and "gdbb" (the gdb built along insight) *are* identical except for one byte which tells "gdbb" to start with the console instead of insight.
    
    "gdb" (the system gdb) and "insight"/"gdb" differ in that the former does not contain any insight code (so "gdb -i insight" won't work as it will for "gdbb"). They also differ slightly because the system gdb, vended by Red Hat, has some modifications to make gdb work differently (often better) than vanilla FSF gdb on linux systems (particularly Red Hat's).
    
    So, in short: the insight and gdb that you built are completely the same. These executables are self-contained. Insight *is* gdb, but with the GUI stuffed into it.
    
    BTW, you can safely use configure's "--prefix" option to have the build install executables in some other place (like /usr/local on unix/linux systems) instead of the system path. If you then add /usr/local/bin in front of your PATH, whenever you type "insight" or "gdb", you will get the version you built. To get the system version, use "/usr/bin/gdb". That's what I do on a daily basis (except I keep insight stored in my home directory somewhere).

http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=349


             reply	other threads:[~2010-04-29 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 21:11 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-29 20:43 Alan Carwile
2010-04-29 20:13 alan

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=20100429211146.3400.qmail@sourceware.org \
    --to=kseitz@sources.redhat.com \
    --cc=alan@carwiles.com \
    --cc=insight-gnats@sources.redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=nobody@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).