Author: labath
Date: Fri Nov 4 06:49:06 2016
New Revision: 285992
URL: http://llvm.org/viewvc/llvm-project?rev=285992&view=rev
Log:
Fix GDBRemoteCommunicationClientTest.TestPacketSpeedJSON
The mock server was listening for only one packet (I forgot to put a loop around
it), which caused the clie
Hi Jason,
Sorry about that. The problem was in the present in the debug builds
only. r285992 should fix it.
pl
On 4 November 2016 at 02:45, Jason Molenda wrote:
> Is anyone else seeing a hang in
> GDBRemoteCommunicationClientTest.TestPacketSpeedJSON when running the unit
> tests? It was a ne
tberghammer added a comment.
My understanding (can be wrong) is that there IS a difference between not
specifying a register in the unwind info versus specifying it as "is same" for
volatile (caller saved) registers. I think for volatile registers not
specifying them means that we can't access
dvlahovski created this revision.
dvlahovski added a reviewer: labath.
dvlahovski added a subscriber: lldb-commits.
The floating-point and SSE registers could be present in the elf-core
file in the note NT_FPREGSET for 64 bit ones, and in the note
NT_PRXFPREG for 32 bit ones.
The entire note is a
Author: enrico
Date: Fri Nov 4 13:15:39 2016
New Revision: 286003
URL: http://llvm.org/viewvc/llvm-project?rev=286003&view=rev
Log:
Preliminary plumbing work to make 'parray' able to take offset and stride
options
Modified:
lldb/trunk/include/lldb/DataFormatters/DumpValueObjectOptions.h
emaste added a comment.
We need to make sure this does not regress FreeBSD core handling -- I will test
as soon as I can, and add FXSAVE parsing for FreeBSD. I'll use fpr_sse.cpp to
generate FreeBSD core files as well (although note that we get ~2.5MB cores
with default configuration, so tweaki
labath added a comment.
I was very successful in creating tiny core files by avoiding linking with the
standard library (you don't really need a full libc to crash :P ).
I think this file should use the same approach as well (see the other core
files in this directory, and the make-core.sh scrip
jasonmolenda added a comment.
Ah, interesting point, I didn't think of that. However, this touches on
another thing I've been thinking about as I look at the assembly inspection
unwind plan generators. In the x86 unwind inspector, I've hardcoded the
SysV-x86_64 ABI and the unwind plan generat
emaste created this revision.
emaste added a reviewer: labath.
emaste added a subscriber: lldb-commits.
https://reviews.llvm.org/D26315
Files:
packages/Python/lldbsuite/test/functionalities/postmortem/linux-core/make-core.sh
Index:
packages/Python/lldbsuite/test/functionalities/postmortem/l
emaste added a comment.
Output on FreeBSD, with the patch:
% sh make-core.sh main.c
+ file=main.c
+ [ -z main.c ]
+ [ FreeBSD '=' Linux ]
+ ulimit -c 1000
+ ulimit -c
+ real_limit=1000
+ [ 1000 -lt 100 ]
+ cc -nostdlib -static -g main.c -o a.out
+ cat
Executable file is in a
emaste added a comment.
Good point. https://reviews.llvm.org/D26315 has the change to add FreeBSD
support to make-core.sh -- just avoiding /bin/bash, and the core file handler
check.
I think we should be able to rename this directory to elf-core, and rename the
individual cores to e.g. linux-i
zturner accepted this revision.
zturner added a comment.
This revision is now accepted and ready to land.
looks good, sorry for the delay was busy with the LLVM dev conference.
Comment at: unittests/SymbolFile/DWARF/SymbolFileDWARFTests.cpp:33-36
+#if defined(_MSC_VER)
+#includ
12 matches
Mail list logo
