Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: "Bill Baxter" <wbaxter@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdbmi.el not working with emacs 22
Date: Wed, 28 Feb 2007 22:48:00 -0000	[thread overview]
Message-ID: <17893.62936.704094.408606@kahikatea.snap.net.nz> (raw)
In-Reply-To: <e86a5fd00702281315s57ed98e7kdadbcac124b10d29@mail.gmail.com>

 > The gdbmi.el file says it should work with emacs 22 by just dropping it in.
 > 
 > I tried it with this emacs 22: http://ourcomments.org/Emacs/EmacsW32.html
 > Using MinGW gdb 6.3-2 from here:
 >      http://prdownloads.sf.net/mingw/gdb-6.3-2.exe?download
 > I downloaded gdbmi.el out of CVS.
 > http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/mi/gdb-mi.el?cvsroot=src
 > 
 > The same gdb/emacs combo works fine with the regular M-x gdb mode and
 > --annotate=3, namely it shows the current line indicator and
 > breakpoints properly.

I'm glad to hear that this works with MinGW.

 > However M-x gdbmi with the default command-line did not work
 > properly.  It is able to debug, but the decorations don't show up in
 > the margin.

Emacs 22 has probably changed too much in CVS in that time.  It *should* work
with latest GDB (6.6) but I don't know if MinGW has such a build.

 > Is this a bug, or a known issue, or what?
 > Should I file a bug report?

Please don't file a bug report.  It does says in the file that it's under
development, but perhaps it should carry a stronger health warning.  If you
want an easy life then use the mode in Emacs 22.  If you want to help develop
gdb-mi.el then, welcome!, but you will need the latest GDB and to post your
findings here.  The plan was/is to keep it synchronised with GDB once Emacs is
released.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-02-28 21:36 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 [this message]
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
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=17893.62936.704094.408606@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --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