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.
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