https://bugs.llvm.org/show_bug.cgi?id=33875
Bug ID: 33875
Summary: TestWithModuleDebugging fails since llvm r308708
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhanceme
I will be on parental leave for the next ~three months. I will take a
peek on the mailing lists from time to time, but my response times
will be unpredictable, and I probably won't be in a position to help
with troubleshooting any linux/android issues.
For the time being, please direct your linux&
The first thing I'd do is use the lldb logging mechanism. lldb-server closes
its own stdout and stderr, because nobody is interested in output from the
server, just from the target. Except when you're debugging the server, so
there is an easy way to turn on logging.
Set the following environment v
There's a function in OptionValueProperties
(http://llvm.org/viewvc/llvm-project/lldb/trunk/source/Interpreter/OptionValueProperties.cpp?view=markup
line 234):
const Property *OptionValueProperties::GetPropertyAtIndex(
const ExecutionContext *exe_ctx, bool will_modify, uint32_t idx)
const
> On Jul 21, 2017, at 4:41 PM, Sean Callanan via lldb-dev
> wrote:
>
> There's a function in OptionValueProperties
> (http://llvm.org/viewvc/llvm-project/lldb/trunk/source/Interpreter/OptionValueProperties.cpp?view=markup
> line 234):
>
> const Property *OptionValueProperties::GetPropertyAtI
Was this just curiosity, or was this getting in your way somehow?
Jim
> On Jul 21, 2017, at 4:50 PM, Jim Ingham via lldb-dev
> wrote:
>
>
>> On Jul 21, 2017, at 4:41 PM, Sean Callanan via lldb-dev
>> wrote:
>>
>> There's a function in OptionValueProperties
>> (http://llvm.org/viewvc/llvm-
I was evaluating whether to provide one in a target setting, and I
decidednot to.
Then I was looking to see why anyone wouild, and I couldn't find anyone
actually using it.
It's a little painful to see it passed around everywhere rather
thanstored by Process or Target, the two thingsthat car
> On Jul 21, 2017, at 4:55 PM, Sean Callanan wrote:
>
> I was evaluating whether to provide one in a target setting, and I decided
> not to.
>
> Then I was looking to see why anyone wouild, and I couldn't find anyone
> actually using it.
>
> It's a little painful to see it passed around ever
If you don't pass an exe_ctx to the Target property setter, it will always set
the global property. If that's what you want that's fine, but be aware that's
what you'll get...
Jim
> On Jul 21, 2017, at 5:00 PM, Jim Ingham wrote:
>
>
>> On Jul 21, 2017, at 4:55 PM, Sean Callanan wrote:
>>
Sadly, that gives me nothing in the log file. Also,
ConnectionFileDescriptor::Connect already seems to handle this case.
Running strace on all child processes gives a “Operation not permitted”
error from setsid(). That seems like the culprit, which is strange.
Would you mind providing the value
Hello,
I was adding support for `SBStructuredData` to my Rust bindings for the
LLDB API and noticed a couple of things.
Since 5.0 isn't out yet and these are newer API additions, I was hoping
there might still be time to fix this.
`SBStructuredData::GetFloatValue` returns a `double`, but other t
11 matches
Mail list logo
