public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Mo DeJong <mdejong@cygnus.com>
To: insight@sources.redhat.com
Subject: Re: Lets rename insight to "insight" (imagine that)
Date: Thu, 16 Nov 2000 14:45:00 -0000	[thread overview]
Message-ID: <Pine.SOL.3.91.1001116143655.1800G-100000@cse.cygnus.com> (raw)
In-Reply-To: <5titpny3eu.fsf@highland.sibyte.com>

> mdejong@cygnus.com (Mo DeJong) writes:

> > What is the cause of these problems? The unfortunate
> > naming of the Insight executable. For some reason
> > it is called "gdb". This is in despite of the fact
> > that it is clearly not the gdb that most people
> > expect to get when typing the command "gdb".
> > 
> > I suggest we change the name of the Insight executable
> > to "insight". This will make things far more intuitive
> > and will save us time and money in the long run.
> > 
> > I would also like to get Insight installed on the
> > default Red Hat release, but that is not currently
> > possible because /usr/bin/gdb is already taken.
> 
> What is /usr/bin/gdb taken by, if not gdb?  and, insight without
> windows _is_ gdb, with some extra mostly-unused stuff thrown in, eh?

The way I see it, Insight is a GUI debugger interface. It also
supports a gdb command line interface when run with the -nw
flag. What distro packager is going to think, hey lets replace
gdb with gdb + some extra mostly-unused stuff thrown in?

> Well, it seems to me that by default, you want to install
> (gdb==insight), under the names gdb and insight, with the former
> providing the normal behaviour, and the latter providing windows.

Nope. By default we should install just the "insight" executable.
We should not clobber the system gdb (by putting our gdb 5.0 on the
PATH).

> It's a shame to have to waste N more megabytes on a gdb binary, when
> insight will do either.


Some on disk numbers from my build:

ls -la ~/project/install/insight/bin/gdb
-rwxr-xr-x    1 mo       mo        8797610 Oct 26 09:36 /home/mo/project/install/insight/bin/gdb

% ls -la /usr/bin/gdb
-rwxr-xr-x    1 root     root      1290416 Mar  7  2000 /usr/bin/gdb


Insight is a lot bigger than command line gdb.

 
> My personal favorite solution (and what I use in my own source trees)
> is to:
> 
> 	* whack top.c so that use_windows = 0 by default.
> 
> 	* install as gdb.
> 
> 	* if insight-style windowing support is present, a simple
> 	script called 'insight' to invoke gdb with the -w flag and the
> 	rest of the remaining script arguments.
> 
> I think, in general, that's probably the appropriate solution to the
> issue.

That would still clobber the existing gdb. It means we can't
make an RPM for Insight because it would conflict with
the /usr/bin/gdb executable from regular gdb.

Mo DeJong
Red Hat Inc

  parent reply	other threads:[~2000-11-16 14:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-16 13:38 Mo DeJong
     [not found] ` <mailpost.974410715.28880@postal.sibyte.com>
2000-11-16 14:10   ` Chris G. Demetriou
2000-11-16 14:22     ` Duane Ellis
2000-11-16 14:45     ` Mo DeJong [this message]
     [not found]       ` <mailpost.974414965.29758@postal.sibyte.com>
2000-11-16 15:32         ` Chris G. Demetriou
2000-11-19  3:24       ` Eray Ozkural (exa)
2000-11-16 15:57 ` Eray Ozkural (exa)
     [not found] <974414704.20985.ezmlm@sources.redhat.com>
2000-11-16 15:20 ` Jim Ingham
2000-11-16 15:39   ` Mo DeJong
     [not found]     ` <mailpost.974418021.30668@postal.sibyte.com>
2000-11-16 18:01       ` Chris G. Demetriou
2000-11-16 16:34 Fabrice Gautier
2000-11-19  3:19 ` Eray Ozkural (exa)

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=Pine.SOL.3.91.1001116143655.1800G-100000@cse.cygnus.com \
    --to=mdejong@cygnus.com \
    --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).