Brian Dessent wrote: > I can't possibly see how this would be due to the changes in newlib, but
Sigh, I knew those sounded like famous last words when I typed them. The actual error was unrelated to this frame, it was occuring several frames up and was a cascading failure that originated with newlib failing to handle the %p printf specifier. In any case it's now fixed in newlib and the next Cygwin snapshot ought to contain the fix. Thanks for testing snapshots. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
