https://sourceware.org/bugzilla/show_bug.cgi?id=32644
--- Comment #4 from Nick Clifton <nickc at redhat dot com> --- (In reply to Michael Matz from comment #3) > Similar to PR32643, shouldn't the error message that's clearly there have > prevented the followup code from running, even in presence of -w? I.e. > like fixed in PR32603? Agreed, that would be the better way to fix this issue. My default thinking however is that all code should be robust, even if it never expects to have to handle bad input. Just relying on earlier code to filter out the bad stuff is never reliable. At least in my opinion. -- You are receiving this mail because: You are on the CC list for the bug.
