Ooh, I'd definitely be interested.
Sounds like a very fun project.
I'll have to familiarize myself with the internals (I'm currently learning
the API, which seems to resemble the internals moderately well...)
I'll start educating myself tomorrow morning when I wake.
-Russell
On Mon, Apr 3, 201
As the person who added most of the support for debugging Windows
executables, I can tell you that I never tested a MinGW executable (nor was
it one of my original goals). It doesn't entirely surprise me that things
are behaving this way, but I'm not sure what the exact cause would be off
the top
BTW, Jason noticed that somebody had deleted the LIBLLDB_LOG_TEMPORARY log
channel.
Since it looks like one of those things that there's no use for, it's easy to
think deleting it is a good cleanup. But it's actually quite useful as a way
to quickly tailor-make a particular set of logs. Som
We'll be at Tied House as usual, starting on Thursday the 6th at 7pm!
If you can, help us plan and RSVP here: http://meetu.ps/37TrcL
See everyone there!
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lld
Also, forgot to include this part: it's pretty important:
PS C:\Users\IEUser> C:\msys64\mingw64\bin\lldb.exe
C:\msys64\home\IEUser\chigraph\build\bin\chi.exe
(lldb) target create
"C:\\msys64\\home\\IEUser\\chigraph\\build\\bin\\chi.exe"
Current executable set to
'C:\msys64\home\IEUser\chigraph\bui
Interesting:
PS C:\Users\IEUser> C:\msys64\mingw64\bin\lldb.exe
C:\msys64\home\IEUser\chigraph\build\bin\chi.exe
(lldb) target create
"C:\\msys64\\home\\IEUser\\chigraph\\build\\bin\\chi.exe"
Current executable set to
'C:\msys64\home\IEUser\chigraph\build\bin\chi.exe' (x86_64).
(lldb) target list
I wonder if lldb isn’t using the windows platform. In the lldb command line,
load up your target, then type “target list”. I’d like to see what plaform it
chose, and what the triple is.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
That makes sense, and I'm sure it works great when using MSVC as a
compiler, but I think LLDB recognizes mingw as a unix compiler and tries to
do GDBRemoteCommunication::StartDebugserverProcess when it should be doing
PlatformWindows::DebugProcess.
Not sure though. All I know is when I try to do a
Hi Russell,
I assume you mean for SBTarget::Launch or LaunchSimple to launch a Windows
application.
The short answer is, this already works.
SBTarget::Launch calls Target::Launch, which calls DebugProcess in the relevant
platform. For cases where we use lldb-server, the platform make
