Date: Sun, 26 Jul 2009 10:19:45 -0600 From: Jamie Gritton <jamie@FreeBSD.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, freebsd-stable <freebsd-stable@FreeBSD.org> Subject: Re: regression with jexec? Message-ID: <4A6C8221.6000807@FreeBSD.org> In-Reply-To: <20090726151245.GM55190@deviant.kiev.zoral.com.ua> References: <4A6B0BD3.6040206@protected-networks.net> <4A6B9A60.90302@FreeBSD.org> <4A6BAC1A.5080303@protected-networks.net> <20090726120608.GE55190@deviant.kiev.zoral.com.ua> <20090726122230.E245@maildrop.int.zabbadoz.net> <4A6C67F5.8080408@FreeBSD.org> <20090726144227.GK55190@deviant.kiev.zoral.com.ua> <4A6C6D27.2030500@FreeBSD.org> <20090726151245.GM55190@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Kostik Belousov wrote: > On Sun, Jul 26, 2009 at 08:50:15AM -0600, Jamie Gritton wrote: >> All true - and I'll add the check you mention to my patch. >> >> But what about the malloc case? Is it equally valid to say that errno >> should not be set when no error occurred? Or are non-syscall libc >> functions generally given free reign to overwrite errno in non-error >> situations? > > Yes, they have a blanket to override errno when no error is returned to > the caller. Malloc is good example. > > Errno is defined only after error. OK then, patching jexec is all that needs doing; I'll get that in. - Jamie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A6C8221.6000807>