On Feb 17, 2015, at 02:42, Jeff King wrote:
On Tue, Feb 17, 2015 at 05:36:30PM +0700, Duy Nguyen wrote:
On Tue, Feb 17, 2015 at 5:13 PM, Jeff King <peff@xxxxxxxx> wrote:
If the only reason is for gdb, then perhaps:
set args pack-objects --stdout </dev/null >/dev/null
in gdb would help?
Right. I used "gdb --args command >/dev/null" instead. Stupid
question. Sorry for the noise.
I've made the same mistake myself many times. I really wish gdb would
interact over /dev/tty by default. The perl debugger does this, and I
find it quite handy. But I've never managed to make gdb do it. Maybe
there is an option I've missed[1].
You may want to try cgdb. It is a curses front-end to gdb. I almost
never run bare gdb anymore. It has a source file pane (no more line-
by-line), a gdb pane and, although a bit clumsy, a TTY pane (not shown
in the screen shot) that you can interact with the debuggee with.
It's been around for a while, so debian-derived distros can usually
just `apt-get install cgdb`. There's a screen shot available [1].
-Kyle
[1] http://cgdb.github.io/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html