>>>>>>>>>> listens 56543 port
>>>>>>>>>
>>>>>>>>> But for 5.0.0 we see it fail the debugserver launch, and get:
>>>>>>>>>
>>>>>>>>>> GDBRemoteCommunication:
b-remote
>>>>>>>>>> process". That's
>>>>>>>>> the channel used in StartDebugServerProcess.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> In fact I have given the rel
StringConvert::ToUInt32(port_cstr, 0);
>>>>>>> if (*port == 0 || *port == child_port) {
>>>>>>>*port = child_port;
>>>>>>>if (log)
>>>>>>> log->Printf("GDBRemoteCommun
gt;>>>>> log->Printf("GDBRemoteCommunication::%s() "
>>>>>> "debugserver listens %u port",
>>>>>> __FUNCTION__, *port);
>>>>>>
>>>>>> As an
gt;>>>>>if (log)
>>>>>> log->Printf("GDBRemoteCommunication::%s() "
>>>>>> "debugserver listens %u port",
>>>>>> __FUNCTION__, *port);
>>>>>>
should error out, not take down lldb.
>>>>
>>>> The assert should be removed and the code should work correctly without
>>>> the assert.
>>>>
>>>>> Another aside, the definition of port_cstr is odd:
>>>>>
>>>>
>>>> Ramana, can you stick in a log message to print port_cstr? I suspect it's
>>>> actually getting 0 back from lldb-server, which would tell us the error is
>>>> in the server code, not the client code.
>>>>
>>>
>&g
.10.12.3:0"
>> argv[3]="--native-regs"
>> argv[4]="--pipe"
>> argv[5]="7"
>> argv[6]=NULL
>>
>> lldb-server should bind to port 0, figure out the port, and write the port
>> number into the file descriptor 7
e/root"
>>> env[13]="LOGNAME=root"
>>> env[14]="SSH_CONNECTION=10.10.33.99 53542 10.10.2.4 22"
>>> env[15]="XDG_RUNTIME_DIR=/run/user/0"
>>> env[16]="_=/mnt/var/binaries/arm_release/bin/lldb-server"
>>> env[17]=NU
tening and accepting a connection
from the remote LLDB.
Greg
> Ted
>
> --
> Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
>> -Original Message-
>> From:
MAIL=/var/mail/root"
> env[7]="PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin"
> env[8]="PWD=/home/root"
> env[9]="EDITOR=vi"
> env[10]="PS1=\u@\h:\w\$ "
> env[11]="SHLVL=1"
> env[12]="HOME=/home/ro
quot;
env[10]="PS1=\u@\h:\w\$ "
env[11]="SHLVL=1"
env[12]="HOME=/home/root"
env[13]="LOGNAME=root"
env[14]="SSH_CONNECTION=10.10.33.99 53542 10.10.2.4 22"
env[15]="XDG_RUNTIME_DIR=/run/user/0"
env[16]="_=/mnt/var/binaries/arm_v5.0_or
ennborg
> Cc: Ramana ; LLDB Dev d...@lists.llvm.org>
> Subject: Re: [lldb-dev] Remote debugging ARM target from x86 host
>
> Port zero should never be returned as a valid port. We do bind to port zero
> just
> so we don't try and pick a port at random just to find it is being used.
Port zero should never be returned as a valid port. We do bind to port zero
just so we don't try and pick a port at random just to find it is being used.
When we bind to port 9, we must find the actual port we bound to and return
that. Seems something has gone wrong with the code that discovers
This was marked as an lldb 5.0.0 release blocker since it's a
regression from 4.0.1: https://bugs.llvm.org/show_bug.cgi?id=34183
lldb-dev: Is there any interest in fixing this bug?
On Fri, Aug 4, 2017 at 10:13 PM, Ramana via lldb-dev
wrote:
> Hi,
>
> I am trying to remote debug ARM (linux) targe
Hi,
I am trying to remote debug ARM (linux) target from x86 (linux) host
and I am getting the following error while trying to launch a process.
The local debugging on ARM works.
error: connect remote failed (invalid host:port specification: '10.10.2.3')
error: process launch failed: invalid host:
16 matches
Mail list logo
