This is the mail archive of the libc-alpha@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]

Re: Fwd: What can a signal handler do with SIGSTKSZ?


On 1/14/19 1:19 PM, Joseph Myers wrote:
> On Mon, 14 Jan 2019, Carlos O'Donell wrote:
> 
>> If *I* were a developer I might expect as Zach pointed out, that I can call
>> every function on the list of callable AS-safe functions, at least once,
>> without recursion, and expect them to operate correctly.
>>
>> A test case for this would therefore be a main, that register a handler
>> that exercises *all* functions in the AS-safe list, and then looks for
>> stack corruption at each execution.
> 
> The POSIX AS-safe list, or the functions that are currently documented as 
> AS-safe in glibc (an observed property, not necessarily a commitment to an 
> API)?  (strtold uses a fair amount of stack, for example, and is listed as 
> AS-safe in glibc.)
 
In the comment above I was only considering the POSIX AS-safe list.

-- 
Cheers,
Carlos.


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