From: Andrew Hall <halla3@corp.earthlink.net>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com, brobecker@gnat.com
Subject: Re: compile error on solaris 8 and 2.6
Date: Wed, 20 Oct 2004 21:36:00 -0000 [thread overview]
Message-ID: <1098304131.27340.140.camel@flagg> (raw)
In-Reply-To: <4176CA13.nail4RV11TEFL@mindspring.com>
Outstanding! That should not be an issue to be missing.
I want to thank everyone for there assistance and willingness to help.
Thank you again very much,
Drew
On Wed, 2004-10-20 at 16:26, Michael Chastain wrote:
> Andrew Hall <halla3@corp.earthlink.net> wrote:
> > Scratch that...it's --disable-tui not --without-tui. So now thats its
> > compiling, what is the impact of disabling tui. What will I not be able
> > to use w/in gdb now that I have disabled tui?
>
> "tui" stands for "text user interface".
>
> The classic gdb interface is the command-line interface.
> It looks like this:
>
> GNU gdb 6.2.50_2004-10-15-cvs
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".
>
> (gdb)
>
> gdbtui looks like this:
>
> âââhello.cââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
> â4 { â
> â5 printf ("hello world\n"); â
> â6 return 0; â
> â7 } â
> â8 â
> â9 â
> â10 â
> â11 â
> â12 â
> â13 â
> â14 â
> â15 â
> â16 â
> âââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
> exec No process In: Line: ?? PC: 0x0
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library
> "/lib/libthread_db.so.1".
>
> That is, it looks more like vi or emacs, and less like a shell session.
>
> Michael
next prev parent reply other threads:[~2004-10-20 20:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 18:34 Andrew Hall
2004-10-20 19:17 ` Joel Brobecker
2004-10-20 19:44 ` Michael Chastain
2004-10-20 20:11 ` Joel Brobecker
2004-10-20 20:26 ` Michael Chastain
2004-10-20 20:29 ` Andrew Hall
2004-10-20 21:19 ` Andrew Hall
2004-10-20 21:22 ` Michael Chastain
2004-10-20 21:36 ` Andrew Hall [this message]
2004-10-20 21:46 ` Andrew Hall
2004-10-20 23:11 ` Michael Chastain
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=1098304131.27340.140.camel@flagg \
--to=halla3@corp.earthlink.net \
--cc=brobecker@gnat.com \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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