On Tue, 5 Jun 2018 at 01:18, Ryan Lovelett via lldb-dev
wrote:
>
> So I've found a capability on Linux to be notified about new processes. I
> have an example of listening for these new processes running on my machine
> now [1] and I can see when my desired user process spawns. Though
> documen
Hi,
On 5 June 2018 at 03:13, Giannis Zamanis via lldb-dev
wrote:
> I have tried using zero-sized type array as
> the typical parameter in the function definition, but when i call the
> function with a normal-sized array as argument it throws error due to
> mismatch in types. I can't find a workar
This error gets printed for all Darwin programs that are not objective C and is
quite annoying in AppleObjCTrampolineHandler.cpp:
if (m_impl_fn_addr == LLDB_INVALID_ADDRESS) {
// If we can't even find the ordinary get method implementation function,
// then we aren't going to be able
Greg,
Something is going wrong here before you get to this point. You can't get to
the code in question (creating the AppleObjCTrampolineHandler) if you don't
have an ObjCLanguageRuntime of some sort. The only way the trampoline gets
made is in ReadObjCLibrary, which is a pure virtual method
Hi,
lldb newbie here.
Has anyone debugged minidump with lldb in MacOS. Any documentation or
pointers would be appreciated!
Thanks,
Rustam
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
I assume you're referring to a windows minidump as opposed to a Mac core
file?
On Tue, Jun 5, 2018 at 4:19 PM Rustam Hashimov via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hi,
> lldb newbie here.
> Has anyone debugged minidump with lldb in MacOS. Any documentation or
> pointers would be apprec
I think I might be a little lost. I built a lldb in debug mode and I am
running lldb in an lldb debugger (very meta).
Earlier in the thread you said "we need a better error message when
vAttachWait returns unsupported" I have found where the error message,
e.g., "error: attach failed: lost connecti
Except for Windows and FreeBSD, lldb uses a server program to do the actual
debugging - either debugserver on Darwin or lldb-server elsewhere. The
interface to these servers (and to the in-process debugging in Windows &
FreeBSD) is abstracted being Process Plugins, which the generic code uses.
Thank you that was a huge help. I'm making some progress now.
Though I wonder, is there any documentation of the GDB packet format? The
reason I ask is that I'm trying to figure out to get the process name from
vAttach.
I've looked at how debugserver does it, namely the method
GetProcessNameF
