| fa72100a0ac0267163cacde1af4ef43822dc390a |
|
27-Jun-2013 |
Han Ming Ong <hanming@apple.com> |
<rdar://problem/14281898>
Much faster way to get dirty size.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@185033 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| 813bec3072bc145dc9d80c5ef04daf8406b91ac0 |
|
26-Jun-2013 |
Han Ming Ong <hanming@apple.com> |
<rdar://problem/14262854>
Match up with top’s implementation on recent Cab as API has changed a bit.
Tested the same binary running on Zin as well. Tested ARM binary on iOS as well.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@185017 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| 3a54da4467c036cf6b8ed4afe5cdd9dd7409c2d5 |
|
23-May-2013 |
Han Ming Ong <hanming@apple.com> |
<rdar://problem/13963648>
Changes after feedback:
Directly use function pointer, just to be safer on 10.8.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@182529 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| 77d340f114b99ec8e2f7a48cbb674c93e237022b |
|
22-May-2013 |
Han Ming Ong <hanming@apple.com> |
<rdar://problem/13963648>
Collect 'anonymous memory' info, if possible
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@182523 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| 08f60c88b61c42c35abf3233f0cbe19d29fbe814 |
|
04-May-2013 |
Jason Molenda <jmolenda@apple.com> |
fix a couple of clang static analyzer warnings.
Most important was a new[] + delete mismatch in ScanFormatDescriptor()
and a couple of possible memory leaks in FileSpec::EnumerateDirectory().
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@181080 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| e255a7d13780e35b97e0f2954cba47cc9eaae7e0 |
|
06-Apr-2013 |
Jason Molenda <jmolenda@apple.com> |
Cache the VM page size that we get from task_vm_info so we don't
re-fetch the value.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@178962 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| dfb7c7f12cbefccf5f097ec90f6d157e2a32f35d |
|
06-Apr-2013 |
Jason Molenda <jmolenda@apple.com> |
Add optional LOG_TASK logging for MachVMMemory::PageSize when the call succeeds, too.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@178955 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| 92748483a4c36e9bf2535abb863dbca1271053a1 |
|
06-Apr-2013 |
Jason Molenda <jmolenda@apple.com> |
Add optional LOG_TASK logging for MachVMMemory::PageSize() task_info call failure.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@178954 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| fb190f3e1ddbaf9fb72e15a96e103de2b9c0dc44 |
|
06-Apr-2013 |
Jason Molenda <jmolenda@apple.com> |
Update MachVMMemory::PageSize to get the page size of a specific process
if we have an updated task_info call available; else fall back to getting
the default host-wide page size.
Update all uses of the vm page size to get it via MachVMMemory::PageSize().
<rdar://problem/13477763>, <rdar://problem/13498504>
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@178953 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| 2a647e4b0eb044cffab5c8c29b6af9ed52129544 |
|
25-Mar-2013 |
Han Ming Ong <hanming@apple.com> |
<rdar://problem/13498504>
Don't hard code vm page size in profiling code
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@177907 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| 190276872994426fb0398e1cf521748249b75875 |
|
16-Mar-2013 |
Han Ming Ong <hanming@apple.com> |
<rdar://problem/13100435>
Don't discount regions that vmmap is not discounting.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@177202 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| a53a76965eb603afe5705c694ee8e3344f91cc61 |
|
13-Mar-2013 |
Han Ming Ong <hanming@apple.com> |
<rdar://problem/13415471>
Don't get dirty page size if we are not going to send it back
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@176992 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| cec43ab7f30085ac7f65a26a58b956a69e363a3b |
|
04-Mar-2013 |
Han Ming Ong <hanming@apple.com> |
<rdar://problem/13338758>
Make it configurable what to profile.
For Mac, we don't use the dirty page size yet and hence there is no need to gather that. This should be way better in not draining the battery since we are operating between 0% to 0.1% on the Mac after this change.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@176451 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| e45c499d61f372cc93abdacf3dbfa9466c412066 |
|
27-Nov-2012 |
Han Ming Ong <hanming@apple.com> |
<rdar://problem/12759744> Provide physical memory distribution as part of profile data
Make use of unix system calls to provide physical memory usage profile data.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@168720 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| 559cf6e8b52b940f5f4362b32d628838d6301e2e |
|
17-Nov-2012 |
Jason Molenda <jmolenda@apple.com> |
Han Ming's commit in r168228 had a bunch of 4-space tabs
in the source files. Expand to spaces. No content changes,
just whitespace.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@168238 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| fb9cee64303d36d6fe5d87e63dd8701d1ddb70a9 |
|
17-Nov-2012 |
Han Ming Ong <hanming@apple.com> |
<rdar://problem/12720514> Sub-TLF: Provide service to profile the inferior
This allows client to query profiling states on the inferior.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@168228 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| 55f768792c75eb5f9474edb09ca416c8737eeac0 |
|
09-Mar-2012 |
Jim Ingham <jingham@apple.com> |
Make debugserver quieter about memory read errors.
<rdar://problem/10681220>
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@152438 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| 1308a9555ad586ff03c8f97bcfe7f3212d06bc86 |
|
12-Dec-2011 |
Greg Clayton <gclayton@apple.com> |
Always return a valid answer for qMemoryRegionInfo if the packet is supported.
We will return a valid range when possible and omit the "permissions" key
when the memory is not readable, writeable or executeable. This will help us
know the difference between an error back from this packet and unsupported,
from just "this address isn't in a valid region".
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@146394 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| d906b1b24a6c838d78039b399ee43dc57598ab52 |
|
09-Dec-2011 |
Jim Ingham <jingham@apple.com> |
Don't spam warnings about not being able to read memory at 0x0.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@146271 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| a9385537809ef342c843c5ab972e513742652047 |
|
18-Nov-2011 |
Greg Clayton <gclayton@apple.com> |
Added optional calls to lldb_private::Process for getting memory region info
from a process and hooked it up to the new packet that was recently added
to our GDB remote executable named debugserver. Now Process has the following
new calls:
virtual Error
Process::GetMemoryRegionInfo (lldb::addr_t load_addr, MemoryRegionInfo &range_info);
virtual uint32_t
GetLoadAddressPermissions (lldb::addr_t load_addr);
Only the first one needs to be implemented by subclasses that can add this
support.
Cleaned up the way the new packet was implemented in debugserver to be more
useful as an API inside debugserver. Also found an error where finding a region
for an address actually will pick up the next region that follows the address
in the query so we also need ot make sure that the address we requested the
region for falls into the region that gets returned.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@144976 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| bcf07b37b3e3cd37ac74cc42c12009f130f185a3 |
|
09-Nov-2011 |
Jason Molenda <jmolenda@apple.com> |
Remove the QAddressIsExecutable packet I added last night.
Add a more general purpose qMemoryRegionInfo packet which can
describe various attributes about a memory region. Currently it
will return the start address, size, and permissions (read, write,
executable) for the memory region. It may be possible to add
additional attributes in the future such as whether the region is
designated as stack memory or jitted code a la vmmap.
I still haven't implemented the lldb side of the code to use this
packet yet so there may be unexpected behavior - but the basic implementation looks
about right. I'll hook it up to lldb soon and fix any problems that crop up.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@144175 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| dc8ff30b6dbe28c851e99712e20c1358eca4709d |
|
08-Nov-2011 |
Jason Molenda <jmolenda@apple.com> |
Add "QAddressIsExecutable" packet to debugserver. Used to test
whether a given address is in an executable region of memory or
not. I haven't written the lldb side that will use this packet it
hasn't been tested yet but it's a simple enough bit of code.
I want to have this feature available for the unwinder code. When
we're stopped at an address with no valid symbol context, there are
a number of questions I'd like to ask --
is the current pc value in an executable region (e.g. did they
jump to unallocated/unexecutable memory? we know how to unwind
from here if so.)
Is the stack pointer or the frame pointer the correct register
to use to find the caller's saved pc value?
Once we're past the first frame we can trust things like eh_frame
and ABI unwind schemes but the first frame is challenging and having
a way to check potential addresses to see if they're executable or
not would help narrow down the possibilities a lot.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@144074 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|
| 24943d2ee8bfaa7cf5893e4709143924157a5c1e |
|
08-Jun-2010 |
Chris Lattner <sabre@nondot.org> |
Initial checkin of lldb code from internal Apple repo.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@105619 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/debugserver/source/MacOSX/MachVMMemory.cpp
|