Re: copyinstr and ENAMETOOLONG

2016-12-02 Thread Jilles Tjoelker
On Fri, Dec 02, 2016 at 10:20:32AM -0600, Eric van Gyzen wrote: > On 11/02/2016 15:33, Jilles Tjoelker wrote: > > On Wed, Nov 02, 2016 at 02:24:43PM -0500, Eric van Gyzen wrote: > >> Does copyinstr guarantee that it has filled the output buffer when it > >> returns ENAMETOOLONG? I usually try to a

Re: copyinstr and ENAMETOOLONG

2016-12-02 Thread Eric van Gyzen
On 11/02/2016 15:33, Jilles Tjoelker wrote: > On Wed, Nov 02, 2016 at 02:24:43PM -0500, Eric van Gyzen wrote: >> Does copyinstr guarantee that it has filled the output buffer when it >> returns ENAMETOOLONG? I usually try to answer my own questions, but I >> don't speak many dialects of assembly.

Re: copyinstr and ENAMETOOLONG

2016-11-02 Thread Jilles Tjoelker
On Wed, Nov 02, 2016 at 02:24:43PM -0500, Eric van Gyzen wrote: > Does copyinstr guarantee that it has filled the output buffer when it > returns ENAMETOOLONG? I usually try to answer my own questions, but I > don't speak many dialects of assembly. :) The few I checked appear to work by checking

copyinstr and ENAMETOOLONG

2016-11-02 Thread Eric van Gyzen
Does copyinstr guarantee that it has filled the output buffer when it returns ENAMETOOLONG? I usually try to answer my own questions, but I don't speak many dialects of assembly. :) I ask because I'd like to make the following change, and I'd like to know whether I should zero the buffer before