This is the mail archive of the
mailing list for the Cygwin project.
Re: Problem w/ gdb 7.3.50-2 under emacs
- From: Ryan Johnson <ryan dot johnson at cs dot utoronto dot ca>
- To: cygwin at cygwin dot com
- Date: Thu, 13 Oct 2011 13:33:08 -0400
- Subject: Re: Problem w/ gdb 7.3.50-2 under emacs
- References: <CAP_ScW024Rb4Y=NJC-QDRTbuShVr1JCKkGTz-WbKcari7ueFbQ@mail.gmail.com> <4E7497DA.email@example.com>
On 17/09/2011 8:51 AM, Ken Brown wrote:
On 9/13/2011 11:48 PM, Bill Priest wrote:
I also encountered problems, though in my case gdb managed not only to
hang, but also took emacs with it... I had to revert to the older version.
I updated gdb to 7.3.50-2 and I can no longer run M-x gdb under
emacs inside rxvt (gdb core dumps). Reverting back to 7.3.50-1 and it
works. The executable being debugged is built with gcc 4.5.3 and gdb
under rxvt and ddd works. Running M-x shell (/bin/sh) gdb also works.
Running M-x gdba fails identically to M-x gdb. The odd thing is
that after "Reading symbols ... done" nothing is typed and the
"Debugger segmentation fault (core dumped) occurs w/o typing a key.
gcc -Wall -g -o t t.c
Current directory is ~/
GNU gdb (GDB) 184.108.40.20610821-cvs (cygwin-special)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
and "show warranty" for details.
This GDB was configured as "i686-cygwin".
For bug reporting instructions, please see:
Reading symbols from /home/wpriest/t.exe...done.
Debugger segmentation fault (core dumped)
I can confirm this. Bug M-x gud-gdb seems to work fine. I realize,
however, that it may not give you the graphical interface that you'd
Notice that when you use M-x gdb, emacs calls gdb with the
--annotate=3 option. A google search suggests that this option is
obsolete. I don't know if that's part of the problem or not. I can
run gdb with that option outside of emacs and it doesn't segfault.
Has anybody figured out what might be causing the issue?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple