Re: gdb and older cygwins

[Michael Chastain <mec.gnu@mindspring.com>]

Fabian Cenedese <Cenedese@indel.ch> wrote:
> PS: The other solution would be to fix the 2.95.3 source about this
> CRLF bug. I looked into the gcc list but couldn't find simple patches,
> I guess it needs a bigger change. If anyone has some hints about it...

Well first, gcc 2.95.3 is no longer supported on Cygwin.
So you are on your own.  But I do have some hints about it.

gcc 2.95.3 has two preprocessors: the old standalone preprocessor
in cccp.c, and the new integrated preprocessor library in cpp*.c.
The old standalone preprocessor is the default.

The old standalone preprocessor is in cccp.  It's all about
'\\' and '\n' and doesn't understand '\r' very well.

I can think of six strategies to try:

(1)  Go into cccp.c and fix every occurrence of '\\' '\n' tests to
     accept '\\' '\r' '\n' as well.

(2)  Hack on safe_read so that it converts "\r\n" => "\n".
     Essentially you need to allocate a private buffer,
     do the raw read into the private buffer, and then translate
     from the private buffer to the caller-supplied buffer.

     A problem occurs when the '\r' happens at the end of one
     read and the '\n' happens at the beginning of the next read.

(3A) Change every occurence of "open" to include O_TEXT as part
     of the mode.  That is what O_TEXT is for!  It ought to work
     great, except that it only works on systems that actually
     support O_TEXT, like Cygwin.  You would still not be able to
     compile your "\r\n" files on a non-Cygwin system with
     gcc 2.95.3.

(3B) Like 3A, only copy a trick from the VMS support code:

       #if defined(__CYGWIN__)
       #define open(fname,mode,prot)  open(fname,(mode|O_TEXT),prot)
       #endif

     That might actually be all the code you need!

(4) Try building gcc with the new integrated preprocessor instead
    of the old standalone preprocessor.  Configure with
    --enable-cpplib or with --disable-cpp --enable-cpplib.
    However, this was all new code in 2.95.3, so it might have
    had new and exciting bugs.

(5) Mount your Cygwin filesystems with the "text" option.
    All Cygwin programs will see "\n" line endings instead of
    "\r\n".  This is likely to fix the problems with gcc,
    but cause other random problems with other random programs.

I would recommend (3B), followed by (1).  (2) is attractive but
if you don't handle the edge case then you will have random
intermittent losses.  (4) and (5) have side effects that you
would have to handle.

Hope this helps,

Michael Chastain