GNU bug report logs - #12180
Fwd: bug#12163: 24.1; Can not input anything or showing none output when debugging c/c++ application.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 12180 in the body.
You can then email your comments to 12180 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: qq510371827 <qq510371827 <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Fwd: bug#12163: 24.1; Can not input anything or showing none output
	when debugging c/c++ application.
Date: Sat, 11 Aug 2012 23:11:33 +0800

[Message part 1 (text/plain, inline)]

emacs 24.1.1(i686-pc-linux-gnu),GTK+ Version 2.24.10 of 2012-07-17 on
berkelium, modified by Debian
GNU gdb (ubuntu/Linaro 7.4-2012.04-0ubuntu2)
ubuntu 12.04 LTS.

2012/8/11 Eli Zaretskii <eliz <at> gnu.org>

> > From: qq510371827 <qq510371827 <at> gmail.com>
> > Date: Sat, 11 Aug 2012 20:32:56 +0800
> >
> > Thanks for your good work. The problem I encountered on windows is just
> as
> > you have described.But on linux(i am running ubuntu 12.04 under
> virtualbox)
> > ,it works for me.
>
> What version of Emacs do you have on Ubuntu, and what version of GDB?
>

[Message part 2 (text/html, inline)]

Message #8 received at 12180 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: qq510371827 <qq510371827 <at> gmail.com>
Cc: 12180 <at> debbugs.gnu.org
Subject: Re: bug#12180: bug#12163: 24.1;
	Can not input anything or showing none output when debugging
	c/c++	application.
Date: Sat, 11 Aug 2012 19:15:05 +0300

> From: qq510371827 <qq510371827 <at> gmail.com>
> Date: Sat, 11 Aug 2012 23:11:33 +0800
> 
> emacs 24.1.1(i686-pc-linux-gnu),GTK+ Version 2.24.10 of 2012-07-17 on
> berkelium, modified by Debian
> GNU gdb (ubuntu/Linaro 7.4-2012.04-0ubuntu2)
> ubuntu 12.04 LTS.

Did you try this in a GUI session or in a TTY?  If in a GUI session,
can you try in a TTY session ("emacs -Q -nw")?

Message #13 received at submit <at> debbugs.gnu.org (full text, mbox):

From: qq510371827 <qq510371827 <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: bug-gnu-emacs <at> gnu.org, 12180 <at> debbugs.gnu.org
Subject: Re: bug#12180: bug#12163: 24.1; Can not input anything or showing
	none output when debugging c/c++ application.
Date: Sun, 12 Aug 2012 09:32:14 +0800

[Message part 1 (text/plain, inline)]

Yes,I have tried that.Both GUI session and TTY session work very well.
2012/8/12 Eli Zaretskii <eliz <at> gnu.org>

> > From: qq510371827 <qq510371827 <at> gmail.com>
> > Date: Sat, 11 Aug 2012 23:11:33 +0800
> >
> > emacs 24.1.1(i686-pc-linux-gnu),GTK+ Version 2.24.10 of 2012-07-17 on
> > berkelium, modified by Debian
> > GNU gdb (ubuntu/Linaro 7.4-2012.04-0ubuntu2)
> > ubuntu 12.04 LTS.
>
> Did you try this in a GUI session or in a TTY?  If in a GUI session,
> can you try in a TTY session ("emacs -Q -nw")?
>

[Message part 2 (text/html, inline)]

Message #19 received at 12180 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: qq510371827 <qq510371827 <at> gmail.com>, Nick Roberts <nickrob <at> snap.net.nz>
Cc: 12180 <at> debbugs.gnu.org
Subject: Re: bug#12180: bug#12163: 24.1;
	Can not input anything or showing none output when debugging c/c++
	application.
Date: Sun, 12 Aug 2012 20:56:38 +0300

> From: qq510371827 <qq510371827 <at> gmail.com>
> Date: Sun, 12 Aug 2012 09:32:14 +0800
> Cc: 12180 <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
> 
> Yes,I have tried that.Both GUI session and TTY session work very well.

I guess it's a matter of timing, then: there's a certain race
condition between Emacs that crams commands into GDB and the debuggee
that reads from stdin.  If the latter comes after Emacs already sent
all the commands, then the program will work correctly.  But that's a
guess; I hope someone knowledgeable about GUD, comint, and gdb-mi will
chime in.  Nick? somebody?

Anyway, I found a work-around for this problem.  After entering GDB,
and before running your program, type this command at GDB prompt:

  (gdb) set new-console on

This will cause GDB to create a separate console window for the input
and output of your program, when you run it, and you can then
communicate with your program without mixing its I/O with that of GDB.
Just be sure to put a breakpoint at the 'exit' call or at the last
line of your 'main' function, if you want to look at the program
output.  If you don't do that, the console will be automatically
closed when your program exits.

Message #22 received at submit <at> debbugs.gnu.org (full text, mbox):

From: qq510371827 <qq510371827 <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>, bug-gnu-emacs <at> gnu.org
Subject: Re: bug#12180: bug#12163: 24.1; Can not input anything or showing
	none output when debugging c/c++ application.
Date: Mon, 13 Aug 2012 22:00:33 +0800

[Message part 1 (text/plain, inline)]

' set new-console on ' command works for me. I have tried eclipse cdt  and
it also has the same problem as emacs 24.1 on windows with mingw.
Strangely, why emacs 23.4 just works?
2012/8/13 Eli Zaretskii <eliz <at> gnu.org>

> > From: qq510371827 <qq510371827 <at> gmail.com>
> > Date: Sun, 12 Aug 2012 09:32:14 +0800
> > Cc: 12180 <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
> >
> > Yes,I have tried that.Both GUI session and TTY session work very well.
>
> I guess it's a matter of timing, then: there's a certain race
> condition between Emacs that crams commands into GDB and the debuggee
> that reads from stdin.  If the latter comes after Emacs already sent
> all the commands, then the program will work correctly.  But that's a
> guess; I hope someone knowledgeable about GUD, comint, and gdb-mi will
> chime in.  Nick? somebody?
>
> Anyway, I found a work-around for this problem.  After entering GDB,
> and before running your program, type this command at GDB prompt:
>
>   (gdb) set new-console on
>
> This will cause GDB to create a separate console window for the input
> and output of your program, when you run it, and you can then
> communicate with your program without mixing its I/O with that of GDB.
> Just be sure to put a breakpoint at the 'exit' call or at the last
> line of your 'main' function, if you want to look at the program
> output.  If you don't do that, the console will be automatically
> closed when your program exits.
>

[Message part 2 (text/html, inline)]

Message #35 received at 12180 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: qq510371827 <qq510371827 <at> gmail.com>
Cc: 12163 <at> debbugs.gnu.org, 12180 <at> debbugs.gnu.org
Subject: Re: bug#12180: Fwd: bug#12163: 24.1; Can not input anything or
 showing none output when debugging c/c++ application.
Date: Mon, 07 Feb 2022 01:05:21 +0100

qq510371827 <qq510371827 <at> gmail.com> writes:

> I am running emacs 24.1 on windows7 32bit with mginw32.When debugging my
> c/c++ application I can not give an iputting and can not see any
> output. For example:
>          ...          //  line 1
>          ...          //  line 2
>          fgets(s,255,stdin); //line 3
>          ...         // line 4
>          ...         //line 5
>          i = 0; // line 6          Breakpoint is at this line.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

Are you still seeing this issue on more recent versions of
Emacs/Windows/Mingw?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #40 received at 12180 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: qq510371827 <qq510371827 <at> gmail.com>
Cc: 12163 <at> debbugs.gnu.org, 12180 <at> debbugs.gnu.org
Subject: Re: bug#12180: Fwd: bug#12163: 24.1; Can not input anything or
 showing none output when debugging c/c++ application.
Date: Mon, 07 Mar 2022 03:37:07 +0100

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> Are you still seeing this issue on more recent versions of
> Emacs/Windows/Mingw?

More information was requested, but no response was given within a
month, so I'm closing this bug report.  If the problem still exists,
please respond to this email and we'll reopen the bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.