The SBDebugger::CreateTarget() call take an "SBError &error" as the last
argument. The error will contain any error message:
lldb::SBTarget
CreateTarget (const char *filename,
const char *target_triple,
const char *platform_name,
bool
Ah, I used CreateTargetWithFileAndArch() and missed this one. Feeling
embarrassed... Thank you!
On Wed, Mar 9, 2016 at 10:10 AM, Greg Clayton wrote:
> The SBDebugger::CreateTarget() call take an "SBError &error" as the last
> argument. The error will contain any error message:
>
> lldb::SBTa
Yep, this is legacy API that must stay in because we had it in our API waaa
back when and we never remove API once it has made it into a build and someone
uses it. We might mark it as deprecated, which we should do to
CreateTargetWithFileAndArch and the other function, but we never remove it
Hello, fellow developers!
I’m trying to debug Unreal Engine 4 sample on Android with LLDB 3.8 build from
source - Win32 x86 liblldb.dll and Android ARM lldb-server : it can’t match the
stripped module libUE4.so running on the device with a full version which is
available on a host.
Unreal Buil
The test traces directory tends to accumulate thousands and thousands of
TestStarted-XXX and TestFinished-XXX files. What purpose do they serve?
I assume it's for trying to figure out why something went wrong. If you
have a TestStarted-123 without a corresponding TestFinished-123, then you
can k
I would be happy to see these files go away if no one is using them...
> On Mar 9, 2016, at 2:32 PM, Adrian McCarthy via lldb-dev
> wrote:
>
> The test traces directory tends to accumulate thousands and thousands of
> TestStarted-XXX and TestFinished-XXX files. What purpose do they serve?
>
Hi,
My colleague is trying to use our lldb IDE attaching to app run/build from
Xcode which failed. I can reproduce this with lldb console:
jeffreytan-mbp:$ ps aux | grep iOSApp
jeffreytan 61816 0.0 0.0 2432772676 s002 S+3:00PM
0:00.00 grep iOSApp
jeffreytan 61806 0.0 0.2
Did you follow the instructions and you have made your "lldb_codesign" code
signing certificate?:
svn cat http://llvm.org/svn/llvm-project/lldb/trunk/docs/code-signing.txt
If you don't do this, your debugserver won't have the ability to debug
anything. If you don't want to do this, you can remo
Hi All
I'm hoping that someone might be able to give me some direction
regarding `Type` resolution from DWARF informationfor functions taking
anonymous structs hidden behind a typedef
e.g.
```
typedef struct {
int i;
float f;
} my_untagged_struct;
void __attribute__((noinline)) myfunc(m
So we ran into a problem where we had anonymous structs in modules. They have
no name, so we had no way to say "module A, please give me a struct named...
nothing in the namespace 'foo'". Obviously this doesn't work, so we always try
to make sure a typedef doesn't come from a module first, by as
Hi Greg, I am using the lldb(/usr/bin/lldb) installed by Xcode not
self-built one. For example, I can use lldb to attach to chrome without any
problem. And I can see the debugserver it uses is from
"/Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/Versions/A/Resources/debugserver".
> On Mar 9, 2016, at 3:04 PM, Jeffrey Tan via lldb-dev
> wrote:
>
> Hi,
>
> My colleague is trying to use our lldb IDE attaching to app run/build from
> Xcode which failed. I can reproduce this with lldb console:
>
> jeffreytan-mbp:$ ps aux | grep iOSApp
> jeffreytan 61816 0.0 0.0 2
Thanks for the info Jim. That answers my questions. I will file a bug for
lldb error message.
On Wed, Mar 9, 2016 at 5:57 PM, Jim Ingham wrote:
>
> > On Mar 9, 2016, at 3:04 PM, Jeffrey Tan via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
> >
> > Hi,
> >
> > My colleague is trying to use our lld
13 matches
Mail list logo
