From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: gdb broken inside emacs (again? still?)
Date: Thu, 10 Nov 2011 02:38:00 -0000 [thread overview]
Message-ID: <4EBB38F7.1020303@cornell.edu> (raw)
In-Reply-To: <4EBB07F6.1010101@cs.utoronto.ca>
On 11/9/2011 6:08 PM, Ryan Johnson wrote:
> On 09/11/2011 5:32 PM, Ken Brown wrote:
>> On 11/9/2011 4:44 PM, Ryan Johnson wrote:
>>> Debugging anything within emacs is thus completely impossible at this
>>> time.
>>
>> cgf has already stated that this will be fixed in the next release of
>> gdb; see
>>
>> http://cygwin.com/ml/cygwin/2011-10/msg00564.html
>>
> Sorry, must have missed that one. Thanks for pointing me at it.
>
>> In the meantime, can't you use gdb 7.3.50-1? If you also have problems
>> with that release, please send detailed instructions for reproducing
>> the problem (starting with emacs -Q).
> No luck:
>
> $ cygcheck -cd | grep gdb
> gdb 7.3.50-1
> libgdbm4 1.8.3-20
> $ emacs -Q -nw
> M-x gdb
> Run gdb (like this): gdb
^^^^^^^^^
That's your problem. You've deleted `--annotate=3' from the prompt
emacs gave you. emacs-23 needs that to be there. M-x gdb works fine
for me like that, using both gdb 7.3.50-1 and 7.3.50-3 (which is now
available). I tested with Cygwin 1.7.9 as well as with the latest snapshot.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-11-10 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 21:44 Ryan Johnson
2011-11-09 22:32 ` Ken Brown
2011-11-09 23:08 ` Ryan Johnson
2011-11-10 2:38 ` Ken Brown [this message]
2011-11-10 3:23 ` Ryan Johnson
2011-11-09 23:59 ` Ryan Johnson
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=4EBB38F7.1020303@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).