On Wed, Dec 5, 2018 at 9:45 AM Pavel Labath wrote:
> On 05/12/2018 18:36, Jonas Devlieghere wrote:
> > I believe that posix doesn't make this guarantee, but that in reality
> > neither linux nor darwin recycles pids before they wrap around?
>
> Yes, linux tries pretty hard to not recycle pids, bu
On 05/12/2018 18:36, Jonas Devlieghere wrote:
I believe that posix doesn't make this guarantee, but that in reality
neither linux nor darwin recycles pids before they wrap around?
Yes, linux tries pretty hard to not recycle pids, but this is hampered
by the fact that the default pid limit is
On Wed, Dec 5, 2018 at 5:01 AM Raphael Isemann via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> @Jonas: Did you confirm it is SIGHUP? I remember that we were not sure
> whether the signal kind was SIGHUP or SIGINT.
>
I'm relatively sure. I added a signal handler to lit and it fires on the
signal.
@Jonas: Did you confirm it is SIGHUP? I remember that we were not sure
whether the signal kind was SIGHUP or SIGINT.
- Raphael
Am Mi., 5. Dez. 2018 um 10:25 Uhr schrieb Pavel Labath via lldb-dev
:
>
> On 05/12/2018 03:49, Jonas Devlieghere via lldb-dev wrote:
> > Hi everyone,
> >
> > Since we swit
On 05/12/2018 03:49, Jonas Devlieghere via lldb-dev wrote:
Hi everyone,
Since we switched to lit as the test driver we've been seeing it getting killed
as the result of a SIGHUP signal. The problem doesn't reproduce on every
machine and there seems to be a correlation between number of occurre
