From: nickrob@snap.net.nz (Nick Roberts)
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: emacs-devel@gnu.org
Subject: Re: GDB on Mac is (NOT) Broken
Date: Mon, 22 Mar 2010 15:32:34 +1300 [thread overview]
Message-ID: <19366.54978.906314.549908@totara.tehura.co.nz> (raw)
In-Reply-To: <wliq8pp2j8.wl%mituharu@math.s.chiba-u.ac.jp>
> I tried your code with removing the line (setq gdb-version "pre-6.4")
> in gdb-apple-test, because set-process-coding-system should go to the
> then-clause.
Yes, it shouldn't be there. Sorry, it was just a cut and paste error
from gdb-get-version.
> (I'm not familiar with this at all, but should Apple versions be
> regarded as pre-6.4? On Mac OS X 10.6, the first line looks like `GNU
> gdb 6.3.50-20050815 (Apple version gdb-1346) (Fri Sep 18 20:40:51 UTC
> 2009)', and `server interpreter mi -stack-info-frame' results in
> `^error,msg="No registers."'.)
Apple generally merge in FSF GDB changes so they are broadly similar. The
pre-6.4 tag is just a crude way of finding what MI features GDB will have and
does this by testing if -stack-info-frame is present. Your actual version is
actually < 6.4 but I think we can leave this as it will be correct to a first
approximation.
> It avoided the hang in completion, but in the
> " *partial-output-yourprog*" buffer, ^M was already added because
> "server show version\n" was executed after "server interpreter mi
> -stack-info-frame\n" which triggered the addition of ^M. How about
> checking the result of "server show version\n" before "server
> interpreter mi -stack-info-frame\n"?
Sure. I don't think it matters to other platforms where it goes.
I think it should go in both the branch and the trunk but I defer to Stefan
or Cyd on the former.
--
Nick http://users.snap.net.nz/~nickrob
next prev parent reply other threads:[~2010-03-22 2:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 6:23 GDB on Mac is (NOT) Broken Nick Roberts
2010-03-15 16:39 ` Chad Brown
2010-03-15 20:17 ` Nick Roberts
2010-03-16 0:18 ` YAMAMOTO Mitsuharu
2010-03-16 2:59 ` Steve Revilak
2010-03-16 5:27 ` Nick Roberts
2010-03-16 8:55 ` Chad Brown
2010-03-16 21:00 ` Nick Roberts
2010-03-20 4:10 ` YAMAMOTO Mitsuharu
2010-03-21 6:50 ` Nick Roberts
2010-03-22 1:29 ` YAMAMOTO Mitsuharu
2010-03-22 2:32 ` Nick Roberts [this message]
2010-03-22 2:46 ` Stefan Monnier
2010-03-22 3:04 ` Nick Roberts
2010-03-22 13:43 ` Stefan Monnier
2010-03-22 20:55 ` Nick Roberts
2010-03-23 1:13 ` Stefan Monnier
2010-03-23 1:55 ` YAMAMOTO Mitsuharu
2010-03-23 2:38 ` Nick Roberts
2010-03-23 3:12 ` Stefan Monnier
2010-03-26 9:02 ` Nick Roberts
2010-03-26 20:20 ` Stefan Monnier
2010-03-27 1:00 ` YAMAMOTO Mitsuharu
2010-03-17 13:30 ` Leo
2010-03-20 19:45 ` Stefan Monnier
2010-03-21 4:43 ` YAMAMOTO Mitsuharu
[not found] <20100314185409.00EDD9B718@mxperim5.sea5.speakeasy.net>
2010-03-15 2:43 ` Steve Revilak
-- strict thread matches above, loose matches on Subject: below --
2010-03-14 0:32 Nick Roberts
2010-03-14 19:45 ` Harald Hanche-Olsen
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=19366.54978.906314.549908@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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.