y helping a lot,
thanks for the help. I'll grab the bug and put up a patch - hopefully
tomorrow.
Thanks,
Howard Hellyer
IBM Runtime Technologies, IBM Systems
Greg Clayton wrote on 11/11/2016 18:07:03:
> From: Greg Clayton
> To: Howard Hellyer/UK/IBM@IBMGB
> Cc: Jim Ingham , lldb
t resume a process in a core file");
}
So I think the correct fix is all three of the above.
Greg
>
> I'll have a go at prototyping the solution to read the SIGINFO structure but
> I'd appreciate any thoughts on which is the "correct" fix.
>
> T
e SIGINFO structure
but I'd appreciate any thoughts on which is the "correct" fix.
Thanks,
Howard Hellyer
IBM Runtime Technologies, IBM Systems
From: Jim Ingham
To: Howard Hellyer/UK/IBM@IBMGB
Cc: lldb-dev@lists.llvm.org
Date: 10/11/2016 18:48
Subject:
I think that approach is kind of a bandaid.
Core files can't resume, so it would be better to figure out why telling a core
file which can't resume to resume caused us to go into a tail spin. That
should just fall out of WillResume returning false or some other better general
signal. Specia
I've been hitting a hang when lldb loads some core dumps created on Linux,
generally those created via gcore.
I found an open bug for this here:
https://llvm.org/bugs/show_bug.cgi?id=26322
and the fix that was suggested there still works. (The patch needs some
tidying up due to the code formatti
