From: Eli Zaretskii <eliz@gnu.org>
To: qq510371827 <qq510371827@gmail.com>
Cc: 12163@debbugs.gnu.org
Subject: bug#12163: 24.1; Can not input anything or showing none output when debugging c/c++ application.
Date: Fri, 10 Aug 2012 12:50:21 +0300 [thread overview]
Message-ID: <837gt7dqjm.fsf@gnu.org> (raw)
In-Reply-To: <CAORnh3guaiS0feFz3kH47fyp3JqkyBtfujKxFQ4TZetwZSjLTA@mail.gmail.com>
> From: qq510371827 <qq510371827@gmail.com>
> Date: Fri, 10 Aug 2012 17:14:14 +0800
>
> > Try invoking GDB from Emacs like this:
> >
> > M-x gud-gdb RET
> >
> > If that doesn't help, either, then I'm clueless, sorry. Perhaps
> > someone else could help.
> >
> Thanks for your patience. It finally works. However, two other new
> problem appeared after using 'gud-gdb'.
> 1).the code, gdb information and out/input datas mixed together in the same
> buffer and 'gdb-many-windows' command didn't work any more.
This is expected. gud-gdb uses the old interface with GDB, which
doesn't support gdb-many-windows.
> 2) You can refer this link:
> http://stackoverflow.com/questions/9676135/gud-gdb-emacs-24-not-working
> The same problem as mine.
No, it isn't the same. Your problem was with getting input and output
to and from the debuggee. The above URL describes a much more serious
problem, whereby Emacs doesn't show the source code of functions you
step through. I don't see any of this in your original bug report
(and it surely works for me on MS-Windows).
As for the original problem: could you please post here a minimal C
program that exhibits the problem with I/O when you use "M-x gdb"? I
will then try to look into the reasons of this and the possible ways
to solve that, when I have time.
Thanks.
next prev parent reply other threads:[~2012-08-10 9:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 14:54 bug#12163: 24.1; Can not input anything or showing none output when debugging c/c++ application qq510371827
[not found] ` <83obmkdoli.fsf@gnu.org>
[not found] ` <CAORnh3gDSy9iG=o8E=Hnx=UaqzM6+Of5iN99-7Gyp46iVVMJHw@mail.gmail.com>
2012-08-10 6:37 ` Eli Zaretskii
2012-08-10 9:14 ` qq510371827
2012-08-10 9:50 ` Eli Zaretskii [this message]
2012-08-10 10:18 ` qq510371827
2012-08-10 17:57 ` Eli Zaretskii
2012-08-11 12:32 ` qq510371827
2012-08-11 14:31 ` Eli Zaretskii
[not found] ` <CAORnh3gFYYVmB7gujppmv3cs6rGm6Dei1vPYxGixtnVLSXrC5w@mail.gmail.com>
2012-08-11 15:11 ` bug#12180: Fwd: " qq510371827
2012-08-11 16:15 ` bug#12180: " Eli Zaretskii
2012-08-12 1:32 ` qq510371827
2012-08-12 17:56 ` Eli Zaretskii
2012-08-13 14:00 ` qq510371827
2022-02-07 0:05 ` bug#12163: bug#12180: Fwd: " Lars Ingebrigtsen
2022-03-07 2:37 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837gt7dqjm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12163@debbugs.gnu.org \
--cc=qq510371827@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).