On 03/12/2018 23:54, Leonard Mosescu wrote:
Yay!
In case anyone is interested in the details, the Breakpad symbol format
is documented here:
https://chromium.googlesource.com/breakpad/breakpad/+/master/docs/symbol_files.md
Thanks, Leonard, I actually didn't know about that document. :) (Th
We'll be at Tied House as usual, starting on Thursday the 6th at 7pm!
If you can, help us plan and RSVP here:
https://www.meetup.com/LLVM-Bay-Area-Social/events/kncsjlyxqbjb/
See everyone there!
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://l
On 03.12.2018 14:04, Hans Wennborg via lldb-dev wrote:
> Hello everyone,
>
> I know 7.0.1 isn't out the door yet, and 8.0.0 isn't due for a while,
> so relax :-) But I would like to get the schedule decided before folks
> disappear over the holidays.
>
> According to the usual schedule, the branc
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 occurrences and
thread count.
Davide and Raphael spent some time
Have you tried an strace to see if it tells you who is sending the signal?
On Tue, Dec 4, 2018 at 6:49 PM Jonas Devlieghere via lldb-dev <
lldb-dev@lists.llvm.org> 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
On Tue, Dec 4, 2018 at 19:11 Zachary Turner via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Have you tried an strace to see if it tells you who is sending the signal?
I used DTrace with the default kill.d script. It shows who sends what
signal and there was nothing interesting other than debugs
Do you know if it’s Darwin specific? If so, maybe someone internally can
offer guidance on how to diagnose (like on the kernel team)?
When you aren’t using the lit driver, does the signal still get delivered
(and we just handle it better), or does it not get delivered at all?
On Tue, Dec 4, 2018 a
On Tue, Dec 4, 2018 at 22:03 Zachary Turner wrote:
> Do you know if it’s Darwin specific? If so, maybe someone internally can
> offer guidance on how to diagnose (like on the kernel team)?
>
Finding that out is part of the reason I sent this mail. We’ve only seen it
on Mac Pros and iMac Pros. I
