From: nickrob@snap.net.nz (Nick Roberts)
To: Jason Rumney <jasonr@gnu.org>, 3650@emacsbugs.donarmstrong.com
Cc: emacs-pretest-bug <emacs-pretest-bug@gnu.org>
Subject: bug#3650: M-x gdb unusable on Windows
Date: Tue, 23 Jun 2009 18:09:39 +1200 [thread overview]
Message-ID: <19008.29091.473126.629092@totara.tehura.co.nz> (raw)
In-Reply-To: <4A3F8EAC.5010009@gnu.org>
Jason Rumney writes:
> Jason Rumney wrote:
> > Kenichi Handa wrote:
> >
> >> By the way, I also installed gdb-6.8-mingw-3.tar.bz2. But,
> >> with "M-x gdb", pp and pr commands doesn't work. They print
> >> nothing. They do work when gdb is invoked from command
> >> line. Do you know what is wrong?
Are you sure they print nothing or is it just that the output isn't
being flushed? The commentary in gdb-ui.el has some advice about using
Emacs and GDB on Windows:
;; If you are using Emacs and GDB on Windows you will need to flush the buffer
;; explicitly in your program if you want timely display of I/O in Emacs.
;; Alternatively you can make the output stream unbuffered, for example, by
;; using a macro:
;; #ifdef UNBUFFERED
;; setvbuf (stdout, (char *) NULL, _IONBF, 0);
;; #endif
;; and compiling with -DUNBUFFERED while debugging.
> > I've often had problems in the past using debuggers under Emacs on
> > Windows (under Emacs 21 and early 22 development versions though, so I
> > haven't tried the new gdb-ui extensively), so I always use the command
> > line.
>
> I just tried it, and it seems to be even worse than I remembered.
Perhaps you mean:
I just tried it, and I can't get it to work.
Asking on this list if others are successfully using it will probably answer
the question as to whether the problem is at your end or not. Saying it
is unusable is a bit cheap.
> Problem 1 is that ...
What version of Emacs are you using?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2009-06-23 6:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AAF9D6C.1040303@gnu.org>
2009-05-04 18:26 ` bug#3208: 23.0.93; Memory full / crash when displaying lots of characters from a large font (like Arial Unicode or Code2000) which is not explicitly selected (on Win32) Michael Schierl
2009-05-05 15:25 ` Jason Rumney
2009-05-05 15:46 ` Jason Rumney
2009-05-19 2:13 ` Kenichi Handa
2009-06-18 5:29 ` Jason Rumney
2009-06-22 5:47 ` Jason Rumney
2009-06-22 11:22 ` Kenichi Handa
2009-06-22 11:51 ` Jason Rumney
2009-06-22 12:51 ` Kenichi Handa
2009-06-22 13:05 ` Jason Rumney
2009-06-22 14:01 ` bug#3650: M-x gdb unusable on Windows Jason Rumney
2009-06-23 1:59 ` Kenichi Handa
2009-06-23 3:37 ` Dan Nicolaescu
2009-06-23 6:22 ` Nick Roberts
2009-06-23 7:38 ` Kenichi Handa
2009-06-23 6:09 ` Nick Roberts [this message]
2009-06-23 7:59 ` Jason Rumney
2009-06-23 13:22 ` Kenichi Handa
2009-06-23 17:08 ` Dan Nicolaescu
2009-06-25 5:50 ` Kenichi Handa
2009-06-25 6:13 ` Nick Roberts
2009-06-25 7:51 ` Kenichi Handa
2019-11-02 6:04 ` Stefan Kangas
2019-11-02 8:41 ` Eli Zaretskii
2022-04-13 0:40 ` Lars Ingebrigtsen
2009-06-24 4:26 ` bug#3208: 23.0.93; Memory full / crash when displaying lots of characters from a large font (like Arial Unicode or Code2000) which is not explicitly selected (on Win32) Kenichi Handa
2009-06-24 10:37 ` Jason Rumney
2009-06-24 11:45 ` Kenichi Handa
2009-06-24 10:43 ` Jason Rumney
2009-06-24 11:55 ` Kenichi Handa
[not found] ` <4A422909.9060800@gnu.org>
2009-06-25 8:10 ` Kenichi Handa
2009-06-25 13:21 ` Jason Rumney
2009-06-26 1:26 ` Kenichi Handa
2009-06-26 5:54 ` Jason Rumney
2009-06-26 13:12 ` Kenichi Handa
2009-07-02 12:13 ` Kenichi Handa
2009-07-02 21:36 ` Stefan Monnier
2009-07-03 2:11 ` Kenichi Handa
2009-09-15 14:05 ` bug#3208: marked as done (23.0.93; Memory full / crash when displaying lots of characters from a large font (like Arial Unicode or Code2000) which is not explicitly selected (on Win32)) Emacs bug Tracking System
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19008.29091.473126.629092@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=3650@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=jasonr@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.