Date: Sun, 05 Jul 2015 21:28:31 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 201367] Reproducible urxvt Artifact Message-ID: <bug-201367-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201367 Bug ID: 201367 Summary: Reproducible urxvt Artifact Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: lens.fbsd@gmail.com Using urxvt, I come across a "D" artifact when coding in C quite often. This happens when I press Ctrl+D during a getchar() while loop that looks for EOF. The following example is a piece of code that's still in progress; it is not correct/complete in and of itself but the problem itself is reproducible using a basic loop for this. (while ((blah = getchar()) != EOF) ...) Code: https://ideone.com/fUEUgw Result: http://ideone.com/Y0rpJw Other people have produced this result on 10.1-RELEASE-P9 (amd64), 11-CURRENT (i386), 10.1-RELEASE (arm), 10.1-RELEASE-P10 and even netbsd-current/amd64. My uname -a: FreeBSD strawberry 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Wed May 13 06:54:13 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201367-13>