Hey,
I noticed that SBProcess::ReadCStringFromMemory uses the deprecated
Process::ReadCStringFromMemory function. The note says that it was
deprecated in favor of ReadStringFromMemory.
Is it possible to add that function to the SBProcess api ?
___
lldb-d
gt;::_M_dispose() () from
>> /usr/lib/liblldb.so.3.8.0
>> #13 0x00007ffff71cdceb in
>> std::vector,
>> std::allocator > >::~vector()
>> () from /usr/lib/liblldb.so.3.8.0
>> #14 0x760d9c38 in __run_exit_handlers () from /usr/lib/libc.so.6
>> #15 0x7
.so.6
#17 0x4f69 in _start ()
2016-03-25 22:42 GMT+01:00 Jim Ingham :
> What version of the lldb sources are you working with? I changed the
> SBListener over to using only the ListenerSP internally
> in r262863.
>
> Jim
>
>> On Mar 25, 2016, at 1:03 PM, Paul
port less useful. Can you go into some detail as to
> why you are trying to do this?
>
> Are you using swig to do the javascript port?
>
> Greg
>
>> On Mar 25, 2016, at 1:03 PM, Paul Peet via lldb-dev
>> wrote:
>>
>> Hey,
>>
>> I am currently wor
the ListenerSP internally
> in r262863.
>
> Jim
>
>> On Mar 25, 2016, at 1:03 PM, Paul Peet via lldb-dev
>> wrote:
>>
>> Hey,
>>
>> I am currently working on lldb bindings for javascript (v8) but it
>> seems that the API is giving me some
Hey,
I am currently working on lldb bindings for javascript (v8) but it
seems that the API is giving me some troubles.
What I am doing is to basically wrap SB* objects into V8 objects, and
since SB objects contain a shared_ptr into an internal class I think I
can simply copy construct them.
To r
68030
>>> (pid = 5862), state = stopped}
>>> Stopped at breakpoint
>>> --
>>> Hello World
>>> ------
>>> * thread #1: tid = 5862, 0x00400978 main`main + 72 at
>>> main.cpp:9, name = 'main', stop reason = ste
Stopped at breakpoint
--
Hello World
--
2016-03-03 14:57 GMT+01:00 Pavel Labath :
> Hi Paul,
>
> I haven't followed this discussion from the start, and I am now having
> trouble understanding what is the issue at hand here. Could you just
> briefly repeat what i
Sorry to bring this up again, but I am not sure if this is really a
linux kernel issue anymore, see the following code:
if(event_type == SBProcess::eBroadcastBitStateChanged) {
const StateType state = SBProcess::GetStateFromEvent(event);
switch(state) {
default:
continue;
case e
um_bytes bytes of the string data
>>>> in buffer
>>>> if (num_bytes > 0)
>>>>printf("%*s", (int)num_bytes, buffer);
>>>>} while (num_bytes == sizeof(buffer);
>>&g
es an invalid thread, sometimes a valid
>>> thread that might be in the middle of a step. When you are stopped, you are
>>> guaranteed to get good results. So make sure you are stopped before you ask
>>> for threads, frames, variables, etc...
>>> 2 - Make sure t
ocation. Sometimes it's still on the same
>> breakpoint line and sometimes it's on the proper next line. How is it that
>> the thread is still changing even if the stopped state event got hit?
>>
>> The code:
>> http://pastebin.com/0arNea9m
>>
>> S
Hello,
I am currently working on an IDE for C++ and I would like to integrate lldb
as a debugger using the C++ API but it has been difficult for me to
understand the architecture because there is no documentation available
(except doxygen which isn't helpful at all).
I am at the point understandin
13 matches
Mail list logo
