; On Nov 4, 2015, at 10:14 AM, Mark Chandler via lldb-dev
> wrote:
>
> Im not sure, but I assume that the kernel writes the core out as the process
> reads it. Will need to dig into the kernel code to confirm.
>
>
> Mark Chandler
> Battle.Net Engineering Systems | B
Im not sure, but I assume that the kernel writes the core out as the process
reads it. Will need to dig into the kernel code to confirm.
Mark Chandler
Battle.Net Engineering Systems | Blizzard Entertainment
(P) 949-955-1380 x15353
-Original Message-
From: Greg Clayton [mailto:gclay...@a
The problem becomes when the core data on stdin is gigabytes in size and there
is little to no diskspace or memory (as the process is still around) to
store/process the data.
Mark Chandler
Battle.Net Engineering Systems | Blizzard Entertainment
(P) 949-955-1380 x15353
-Original Message
frames up and symbolicate up the crash location. It should be
>>> just as good as having the process around without any bad side affects.
>>> Core files are less useful if they must be archived and symbolicated later
>>> because the executable files might not be aro
;> so you can get symbols and use the debug info, so LLDB should be able to
>> load all frames up and symbolicate up the crash location. It should be just
>> as good as having the process around without any bad side affects. Core
>> files are less useful if they must b
ht produce binaries for testing and remove them after the test is run or
> crashed.
>
> What do you think about this approach?
>
> Greg Clayton
>
>
>> On Nov 2, 2015, at 5:54 PM, Mark Chandler via lldb-dev
>> wrote:
>>
>> So im trying to write
testing and remove them after the test is run or crashed.
What do you think about this approach?
Greg Clayton
> On Nov 2, 2015, at 5:54 PM, Mark Chandler via lldb-dev
> wrote:
>
> So im trying to write a core handler program and use lldb to attach and dump
> important information
So im trying to write a core handler program and use lldb to attach and dump
important information about it. This works if a use my tool to attach to an
existing one but I found that lldb-server will hang in a waitpid call if the
kernel has invoked the tool after another process has cored.
Exam
want to build the ninja build tool to optimize your
build speed and use -GNinja with your cmake command line.
It'll be interesting to hear what else you find.
On Tue, Oct 27, 2015 at 8:37 PM, Mark Chandler via lldb-dev
mailto:lldb-dev@lists.llvm.org>> wrote:
Using gcc 4.8 from de
it via DCMAKE_C_COMPILER and DCMAKE_CXX_COMPILER flags?
It might be a problem with sysroot setup since some headers are not found - you
can try to pass a custom sysroot with -DCMAKE_CXX_FLAGS="--sysroot=..."
On Tue, Oct 27, 2015 at 2:05 PM, Mark Chandler via lldb-dev
mailto:lldb-dev@lists.
Hi All,
Trying to get LLDB to compile on centos 5 to help reduce the size of cores of
programs crashing on some servers however im running into some compile issues
with it. Looks like some features are used from newer kernel versions and was
wondering what the procedure is to get this fixed and
11 matches
Mail list logo
