John Baldwin writes:
> On 2/15/19 8:43 AM, Christian Barthel wrote:
>> John Baldwin writes:
>>
>>> See the siginfo(3) manpage. SI_TIMER is described there as:
>>>
>>> SI_TIMER signal generated by expiration of a
>>> timer set by timer_settime(2)
>>>
>>>
On 2/15/19 8:43 AM, Christian Barthel wrote:
> John Baldwin writes:
>
>> See the siginfo(3) manpage. SI_TIMER is described there as:
>>
>> SI_TIMER signal generated by expiration of a
>> timer set by timer_settime(2)
>>
>> It is not for setitimer. Simila
John Baldwin writes:
> See the siginfo(3) manpage. SI_TIMER is described there as:
>
> SI_TIMER signal generated by expiration of a
> timer set by timer_settime(2)
>
> It is not for setitimer. Similarly, si_addr is usually only specified for
> synchronou
On Thu, Feb 14, 2019 at 4:50 AM Christian Barthel wrote:
> Hello,
> I am interested in the historical development of the siginfo_t
> record. I hope, this is the correct mailinglist and there are
> still readers on it.
>
The historical development of siginfo_t is actually quite interesting. I'm
On 2/14/19 1:50 AM, Christian Barthel wrote:
> Hello,
> I am interested in the historical development of the siginfo_t
> record. I hope, this is the correct mailinglist and there are
> still readers on it.
>
> I've tried to write a very simple and minimalistic profiler for a
> single threaded a
Hello,
I am interested in the historical development of the siginfo_t
record. I hope, this is the correct mailinglist and there are
still readers on it.
I've tried to write a very simple and minimalistic profiler for a
single threaded application by using setitimer(2) and SIGPROF
signal. When
