Displaying 5 results from an estimated 5 matches for "jingham".
Did you mean:
bingham
2018 Jun 26
4
[lldb-dev] RFC: libtrace
...ands.
>>
>> It will probably be useful someday to have an expression parser and language specific type system, but when that comes I don't think we'd want anything radically different than what LLDB already has.
>>
>> On Tue, Jun 26, 2018 at 12:26 PM Jim Ingham <jingham at apple.com> wrote:
>> Just to be clear, by "no clang integration" do you mean "no expression parser" or do you mean something more radical? For instance, adding a TypeSystem and its DWARF parser for C family languages that uses a different underlying representation t...
2018 Jun 26
2
[lldb-dev] RFC: libtrace
...these into types that clang understands.
It will probably be useful someday to have an expression parser and
language specific type system, but when that comes I don't think we'd want
anything radically different than what LLDB already has.
On Tue, Jun 26, 2018 at 12:26 PM Jim Ingham <jingham at apple.com> wrote:
> Just to be clear, by "no clang integration" do you mean "no expression
> parser" or do you mean something more radical? For instance, adding a
> TypeSystem and its DWARF parser for C family languages that uses a
> different underlying repr...
2015 May 18
2
[LLVMdev] Crash reporting in clang/lldb
+llvmdev
-llvm-dev
On Mon, May 18, 2015 at 4:28 PM, Vince Harron <vince at nethacker.com> wrote:
> Hi all,
>
> I would like to integrate crash reporting into Android developer tools,
> starting with lldb and clang. Google Breakpad seems like a reasonable
> option.
>
> https://code.google.com/p/google-breakpad/
>
> Of course, it will only be enabled when the
2018 Apr 17
1
[lldb-dev] lldb stops on every call to dlopen
It is interesting that the stop reason on the thread that stopped is "trace". That's what you would expect returning from the single-step to step over the breakpoint. But it looks like we got a signal while single-stepping, but the stop reason was misreported by somebody.
Jim
> On Apr 17, 2018, at 6:00 AM, Pavel Labath via lldb-dev <lldb-dev at lists.llvm.org> wrote:
2018 Jun 26
4
RFC: libtrace
Hi all,
We have been thinking internally about a lightweight llvm-based ptracer.
To address one question up front: the primary way in which this differs
from LLDB is that it targets a more narrow use case -- there is no
scripting support, no clang integration, no dynamic extensibility, no
support for running jitted code in the target, and no user interface. We
have several use cases internally