Mail Archives: djgpp-workers/2016/04/25/12:05:23
Sent to me privately. I suggested author to send it to list. I have not seen however any activity
since that.
So I'm forwarding message to list.
I'm also committing the proposed patch for ttyscrn.c.
Andris
-------- Forwarded Message --------
Subject: A few DJGPP libc.a bugs
Date: Sun, 27 Mar 2016 20:41:34 +0200
From: felix <felix DOT von DOT s AT posteo DOT de>
To: andris DOT pavenis AT iki DOT fi
Hello,
I'd like to report two bugs in DJGPP 2.05 libc.a. While I have found a
bug tracker of sorts at <http://www.delorie.com/djgpp/bugs/>, it looks
quite untended, to say the least. On the other hand, I found your
address with the recent DJGPP release announcements, so I figure if I
send this here someone might read it.
One of them is a simple typo.
--- src/libc/posix/termios/ttyscrn.c
+++ src/libc/posix/termios/ttyscrn.c
@@ -464,7 +464,7 @@
__dpmi_int(0x10, &r);
if (++(*col) > __tty_screen.max_col)
{
- col = 0;
+ *col = 0;
++row;
}
__tty_screen.set_cursor(*col, *row);
The other one is more complicated. The fseeko64() function, unlike plain
fseek(), doesn't take care of the FILE* buffer, which may cause later
reads to return invalid data. I found this one after cross-compiling gdb
for DOS on my own.
May I suggest putting djcrx and djlsr on savannah.nongnu.org or
wherever?And maybe changing VCSes on the way...
--f
- Raw text -