On 06/07/2011 3:09 AM, Corinna Vinschen wrote:
On Jul 6 02:06, Ryan Johnson wrote:
Hi all,
I've been using gcc-4.5.0 happily for a while, but today I had to
break out gdb to chase down a seg fault. Unfortunately, gdb was
getting line numbers completely wrong, so I had to revert to gcc-4.3
to work through my bug.
Has anybody else seen this? If not, and if it's not trivial to
reproduce, I can cook up a minimal test case.
The debug info in gcc-4.5 has changed in a way which older GDBs don't
understand. You can build GDB 7.2 yourself, that should help.
Actually, Chris, we're still on GDB 6.8. Any chance we can get an
official 7.2 release?
Doh!
I wondered if that was it, but there wasn't an updated gdb available
(experimental or otherwise). Silly thing is, I probably have a gdb-7.2
sitting around somewhere that I didn't think to try.
Thanks,
Ryan
--
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
