From: Phi Debian <phi.debian@gmail.com>
To: Ivo Raisr <ivosh@ivosh.net>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>, brlongbons@gmail.com
Subject: Re: [C++] System Requirements
Date: Mon, 16 Dec 2013 13:52:00 -0000 [thread overview]
Message-ID: <CAJOr74hR1gotrG5x84vb3k2nQxHsUCQQjxGkYE7qbmcsExVwYQ@mail.gmail.com> (raw)
In-Reply-To: <CANXv6=uysZRNXFvbcr+FsxP2iFsabEL43GG=NDwf6_z8VCYYbg@mail.gmail.com>
This is indeed a sad day. I got my own gdb since years, have my own
hack in there, basically getting rid of the TUI and getting my own
proper TUI, not curses based, working much like dbx, xdb, i.e
lightweigth comunication (not graphic) yet able to display source code
efficiently with basic terminal. My hack are 'gdb portable' i.e
forward ported since age. And I only debug C code (so far I was lucky)
This move to gdb written in C++ will indeed move me away from it, time
to look llvm closer :)
May be this will trig also some fork, who knows may be there are some
out there who still want a lightweigth debugger of classic non object
language (say C, pascal, fortran)....
Sounds like GDB caught the same disease as gnome, etc, they want to be modern :)
Cheers,
Phi
next prev parent reply other threads:[~2013-12-16 13:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 0:34 Ben Longbons
2013-12-14 0:40 ` Ben Longbons
2013-12-15 12:28 ` Michael Veksler
2013-12-17 2:29 ` Andrew Pinski
2013-12-17 4:02 ` Ben Longbons
2013-12-18 12:47 ` Michael Veksler
2013-12-18 19:16 ` Ben Longbons
2013-12-15 15:31 ` Jan Kratochvil
2013-12-15 17:04 ` Ben Longbons
2013-12-15 19:53 ` Mark Kettenis
2013-12-16 13:03 ` Ivo Raisr
2013-12-16 13:52 ` Phi Debian [this message]
2013-12-17 5:35 ` Sergio Durigan Junior
2013-12-16 19:10 ` Eli Zaretskii
2013-12-16 20:09 ` Ben Longbons
2013-12-16 19:05 ` Eli Zaretskii
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=CAJOr74hR1gotrG5x84vb3k2nQxHsUCQQjxGkYE7qbmcsExVwYQ@mail.gmail.com \
--to=phi.debian@gmail.com \
--cc=brlongbons@gmail.com \
--cc=gdb@sourceware.org \
--cc=ivosh@ivosh.net \
/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