From: Nick Roberts <nickrob@snap.net.nz>
To: "Bill Baxter" <wbaxter@gmail.com>
Cc: "Daniel Jacobowitz" <drow@false.org>, gdb@sourceware.org
Subject: Re: gdbmi.el not working with emacs 22
Date: Thu, 01 Mar 2007 02:21:00 -0000 [thread overview]
Message-ID: <17894.14489.656676.837961@kahikatea.snap.net.nz> (raw)
In-Reply-To: <e86a5fd00702281800m78a338a2g7d465138a28707d5@mail.gmail.com>
> > I'm not sure that Bill has the latest gdb-mi.el from CVS.
>
> I downloaded 1.11 from the CVS web interface:
> http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/mi/gdb-mi.el?cvsroot=src
>
> But it does indeed seem to be different from the version you sent. Is
> the web interface to CVS not showing the latest?
I don't know what you got but I'm pretty sure that I sent you 1.11.
> > I think some of the problems come from the versions of the gdb and emacs
> > executables. So I have privately sent him the latest gdb-mi.el as it
> > might just work (as an update to Emacs), although it's probably unlikely.
>
> No it didn't fix the problems. Debugging with cygwin's gdb 6.5.50
> seems the same. Breakpoint display works, but current line does not.
>
> BUT -- I just tried this -- it seems that cygwin's gdb 6.5.50 doesn't
> work with regular M-x gdb and --annotate=3 mode either. So maybe
> there's something else going on there, like line-ending conversion
> problems.
This excerpt from gdb-ui.el might be relevant. (I think Windows doesn't have
ttys but uses pipes instead).
;;; Windows Platforms:
;; 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.
> Or not. FWIW, here's the console output of cygwin's GDB 6.5.50:
> --------------------------------
>...
> ----------------------------------------------------
>
> And also FWIW here's what MinGW's gives:
> ------------------------------------------------------
>...
I think these differences are due to version changes in GDB, not cygwin/MinGW
> Anyway, is there concise spec for GDB/MI anywhere that a developer
> trying to implement a the interface can follow?
Yes, under GDB/MI in the GDB manual.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-03-01 2:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 21:37 Bill Baxter
2007-02-28 22:48 ` Nick Roberts
2007-03-01 0:01 ` Bill Baxter
2007-03-01 0:05 ` Daniel Jacobowitz
2007-03-01 0:12 ` Bill Baxter
2007-03-01 0:32 ` Daniel Jacobowitz
2007-03-01 0:57 ` Bill Baxter
2007-03-01 1:09 ` Bill Baxter
2007-03-01 1:18 ` Daniel Jacobowitz
2007-03-01 1:28 ` Nick Roberts
2007-03-01 2:00 ` Bill Baxter
2007-03-01 2:21 ` Nick Roberts [this message]
2007-03-01 4:43 ` Eli Zaretskii
2007-03-01 0:31 ` Nick Roberts
2007-03-01 4:28 ` Eli Zaretskii
2007-03-01 4:15 ` Eli Zaretskii
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=17894.14489.656676.837961@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=wbaxter@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox