Thanks for the suggestions.
I’m working on native support for FreeBSD lldb-server, and wanted to have an
option to build it both ways until it’s stable enough to replace current
implementation. I’ll have it in a separate directory.
On Dec 1, 2016, at 2:55 AM, Pavel Labath
mailto:lab...@google.
https://llvm.org/bugs/show_bug.cgi?id=28055
lab...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
I'm curious, can you share how did you deal with the fact that the
gdb-remote protocol is very signal-centric? E.g. every stop-reply ($T) has
to have a specific signal associated with it, and some signals have special
meaning in lldb. Do you just fake the signal numbers when you need to? Or
is the
The way we have done this with Linux native register contexts was to
notionally leave the files in the build, but completely #ifdef out their
contents (see NativeRegisterConextLinux_arm.cpp).
It's not very nice, but I think it's better than having six subfolders,
each with a single cpp file. If you
