From: Daniel Jacobowitz <drow@false.org>
To: Bill Baxter <wbaxter@gmail.com>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb@sourceware.org
Subject: Re: gdbmi.el not working with emacs 22
Date: Thu, 01 Mar 2007 00:32:00 -0000 [thread overview]
Message-ID: <20070301003249.GA28941@caradoc.them.org> (raw)
In-Reply-To: <e86a5fd00702281611x2c4ad514j29ea6227ec6e9113@mail.gmail.com>
On Thu, Mar 01, 2007 at 09:11:47AM +0900, Bill Baxter wrote:
> On 3/1/07, Daniel Jacobowitz <drow@false.org> wrote:
> >On Thu, Mar 01, 2007 at 09:00:46AM +0900, Bill Baxter wrote:
> >> >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.
> >>
> >> No 6.2.3 is the latest snapshot. So you suspect 6.2.3's MI output is
> >> to old to work with the current emacs code?
> >
> >What do you mean by 6.2.3? Please see http://sourceware.org/gdb/ to
> >get a current release of GDB - I do not know of any with that version
> >number.
>
> Sorry I meant 6.3.2.
Same problem, same advice. The latest release of GDB is version 6.6.
I suspect you're looking at some older MinGW package.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-01 0:32 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 [this message]
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=20070301003249.GA28941@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
--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