From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Doug Lewan Newsgroups: gmane.emacs.help Subject: RE: [h-e-w] Emacs gdb interface Date: Wed, 21 Mar 2012 13:32:33 +0000 Message-ID: <495248DFDEA08C469BBDED2D4AA6C61440998F@DAKIYA1.pegasus.local> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1332336647 19841 80.91.229.3 (21 Mar 2012 13:30:47 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 21 Mar 2012 13:30:47 +0000 (UTC) To: "help-gnu-emacs@gnu.org" Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Mar 21 14:30:46 2012 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SALcc-0003NN-Tw for geh-help-gnu-emacs@m.gmane.org; Wed, 21 Mar 2012 14:30:39 +0100 Original-Received: from localhost ([::1]:44868 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SALcc-0005Wc-82 for geh-help-gnu-emacs@m.gmane.org; Wed, 21 Mar 2012 09:30:38 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:56232) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SALcS-0005V8-4i for help-gnu-emacs@gnu.org; Wed, 21 Mar 2012 09:30:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SALcI-00043U-Am for help-gnu-emacs@gnu.org; Wed, 21 Mar 2012 09:30:27 -0400 Original-Received: from mailhost.shubertorg.com ([207.246.209.200]:43343 helo=webmail.shubertorg.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SALcI-00042v-6S for help-gnu-emacs@gnu.org; Wed, 21 Mar 2012 09:30:18 -0400 Original-Received: from dakiya1.pegasus.local ([fe80::5ce2:4641:22cf:ff1f]) by DAKIYA1.pegasus.local ([::1]) with mapi id 14.01.0339.001; Wed, 21 Mar 2012 09:32:33 -0400 Thread-Topic: [h-e-w] Emacs gdb interface Thread-Index: AQHNBteB2FGE31VDz0WQ0MjYf+kCo5Z0pfFVgABGywD//8tFIA== In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.21.202] X-detected-operating-system: by eggs.gnu.org: Windows XP/2000 (RFC1323+, w+, tstamp-) X-Received-From: 207.246.209.200 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:84069 Archived-At: 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 , invoking (comint-send-input) and as a consequence calls the comint-inpu= t-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 s= how you: Get a shell buffer and type 'stty sane'. (This cooks the terminal. Comint i= ntentionally 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=3Dshubertticketing.com@gnu.org [mailto:h= elp-gnu-emacs-bounces+dougl=3Dshubertticketing.com@gnu.org] On Behalf Of Da= ni 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. --=20 Dani Moncayo