RE: [h-e-w] Emacs gdb interface

[Doug Lewan]

I don't think this will be regarded as a bug.

Debugger mode is derived from comint mode which, by design, doesn't display 
output until it gets to the end of a line.

A few details, if you care:

>From the other side, gdb doesn't see anything you type until you type <ENTER>, 
>invoking (comint-send-input) and as a consequence calls the 
>comint-input-filter-functions.
I think the corresponding function for output is (comint-output-filter).
These things usually do good things for you, like hide passwords.

An experiment (under *NIX), if you want an example of what comint doesn't show 
you:

Get a shell buffer and type 'stty sane'. (This cooks the terminal. Comint 
intentionally makes it raw to control I/O.
Now type a command like 'echo Your name here.'
You will also see the command since the terminal now echoes its input too.
(No, I don't know how to do this on Windows and I don't know something that 
corresponds for gdb. Sorry.)

I hope this helps.

,Doug

-----Original Message-----
From: help-gnu-emacs-bounces+dougl=shubertticketing.com@gnu.org 
[mailto:help-gnu-emacs-bounces+dougl=shubertticketing.com@gnu.org] On Behalf Of 
Dani Moncayo
Sent: Wednesday, 2012 March 21 08:11
To: Sergei Organov
Cc: help-emacs-windows@gnu.org; help-gnu-emacs@gnu.org
Subject: Re: [h-e-w] Emacs gdb interface

> Did you try to run it under bare gdb (without Emacs)? If the problem
> remains, it's gdb issue rather than Emacs one.

Good question.  I've just debugged the program directly under gdb
(invoked from a cmd.exe console) and everything looks fine (I see the
"hello, world" message).

I'm beginning to consider sending an bug report.

Thanks.

-- 
Dani Moncayo