ke putting binaries to the repository because they are not
human readable so it is hard to review/diff them and they will only run on a
single platform and a single architecture while we support a lot of different
configuration.
Tamas
On Wed, Jul 6, 2016 at 3:26 PM E BOUTALEB via lldb-dev
wrote:
I
g binaries to the repository because they are not
human readable so it is hard to review/diff them and they will only run on a
single platform and a single architecture while we support a lot of different
configuration.
Tamas
On Wed, Jul 6, 2016 at 3:26 PM E BOUTALEB via lldb-dev
wrote:
I
I would like to submit two patches for code review.
They introduce concrete support for OCaml native debugging, granted that you
have access to the native compiler with DWARF emission support (see
https://github.com/ocaml/ocaml/pull/574)
This adds about 2000 lines of code.
The type system isn't
swift we would handle:
>
> (lldb) b b.c
>
> as "look for 'c'" and then "make sure any matches contain 'b.c'".
>
> Can you give some examples of your mangle named and how it would look when
> demangled? It might help me guide my respon
I am currently working on a language plugin for lldb.
I would like to be able to put a breakpoint on demangled function names, but
even after demangling function names through my custom DWARF parser, lldb won't
autocomplete on demangled names nor break on them.
I though about modifiying the Inde
