Date: Fri, 4 Dec 1998 16:01:06 +0200 (EET) From: "Kari E. Hurtta" <Kari.Hurtta@ozone.fmi.fi> To: toasty@home.dragondata.com (Kevin Day) Cc: hurtta+elm@ozone.fmi.fi, yk@info.dgtu.donetsk.ua, freebsd-bugs@FreeBSD.ORG Subject: Re: [BUG ?] Segment Violation signal! Message-ID: <199812041401.QAA08065@ozone.fmi.fi> In-Reply-To: <199812041356.HAA18428@home.dragondata.com> from Kevin Day at "Dec 4, 1998 07:56:34 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Day: > > Kevin Day: > > > > > > To add to this... Just receiving your message crashed my elm. :) > > > > Decoding on encoding someway corrupt memory: > > > > I just received this response from the elm author: > > > > Subject: Re: Elm crash bug > To: toasty@home.dragondata.com (Kevin Day) > Date: Fri, 4 Dec 1998 08:51:18 -0500 (EST) > Reply-To: syd@myxa.com > > well known, elm uses fixed length buffers, that is why we wanted a > rewrite of the base elm code, which won't happen, this bug will probably > never be fixed. That is readon, why I have on my ME+ code bound checking when writing buffers. But there of course may be some places which I have missed... (just replacing strcpy:s, strcat:s and sprintf:s is not enough.) Note that that crash did not occured on official elm, but on my ME+ version. In officail version do not even have that mime decoding code... / Kari Hurtta To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812041401.QAA08065>