Am sorry I can't commit build resources, but am certainly willing to commit
time to solving test problems. In a very general sense, I think our project
(Ghidra) will effectively be a test platform for issues with the Java bindings
to SWIG.
With regard to the set-up for testing, I have noticed
Hi Jonas,
Apologies for the non-build - I did a fetch/rebase this morning before creating
the patch. Do I need to be on a different branch re StringRef vs ConstString?
(Have seen that discussion in passing but confess I did not follow it in
detail.) Any pointers appreciated.
Re testing, I
Just to clarify my use case: I am one of the developers for a
reverse-engineering tool called Ghidra. Part of the tool is debugging-support
to allow cross-over between dynamic and static analysis. We currently support
windbg/kd, the gcc MI2 interface, and direct Java debugging. I have a work
I'm not sure I understand your testing strategy, in particular how it applies
to the existing Lua and Python extensions. I am looking at the files in
lldb/unittests/ScriptInterpreter/Lua&Python. Do you execute test from native
Lua/Python environments or through C wrappers-only? You mentioned
Merde - I followed you instructions but forgot to run clang-format. Give me a
minute
From: Raphael Isemann via Phabricator
Sent: Friday, October 8, 2021 11:24:10 AM
To: David Millar; anoro...@apple.com; fallk...@yahoo.com; kkle...@redhat.com;
medismail.benn
Am obviously brand new to your process and a bit of an old dog when it comes to
learning new tricks. Would you prefer I make a new submission with the
-U99 diff? Also, am more than willing to help with the Java tests if that
would be useful.
From: Raphael
