Date: Sat, 25 Feb 2006 16:32:17 -0600 (CST) From: Stephen Montgomery-Smith <stephen@cauchy.math.missouri.edu> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/93841: seg fault with dmesg Message-ID: <200602252232.k1PMWHmX092909@cauchy.math.missouri.edu> Resent-Message-ID: <200602252240.k1PMe6NR021909@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 93841 >Category: bin >Synopsis: seg fault with dmesg >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Feb 25 22:40:06 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Stephen Montgomery-Smith >Release: FreeBSD 6.1-PRERELEASE i386 >Organization: >Environment: System: FreeBSD cauchy 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Sun Feb 5 02:37:31 CST 2006 stephen@cauchy:/usr/obj/usr/src/sys/cauchy i386 >Description: My video card issues some really weird messages to the message buffer, e.g. < 2>> When the message buffer has such problems, dmesg will seg fault. >How-To-Repeat: I'm not sure how anyone else could mimic this problem. >Fix: --- dmesg.c-orig Sat Feb 25 16:26:18 2006 +++ dmesg.c Sat Feb 25 16:27:01 2006 @@ -177,7 +177,7 @@ nextp++; /* Skip ^<[0-9]+> syslog sequences. */ - if (*p == '<') { + if (*p == '<' && *(p+1) != '\n') { errno = 0; pri = strtol(p + 1, &q, 10); if (*q == '>' && pri >= 0 && pri < INT_MAX && >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602252232.k1PMWHmX092909>