This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/20326] Segment fault in execvpe.c


https://sourceware.org/bugzilla/show_bug.cgi?id=20326

--- Comment #7 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to n0va8o.lau from comment #6)
> (In reply to Florian Weimer from comment #5)
> > (In reply to n0va8o.lau from comment #4)
> > > (In reply to Andreas Schwab from comment #3)
> > > > Don't do that then.  The arguments must not be null.
> > > 
> > > don't you think it's better to add a check in execvp please?
> > 
> > How did you notice this problem?  It is difficult to see what value NULL
> > checks add in such cases.
> 
> I got it when I debug.

Sorry, I do not quite understand.  Debugging what?  Your own code you just
wrote?

In such cases, a straight crash is usually preferred to returning an error code
which the caller may neglect to check.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]