[lldb-dev] Remote debugging a docker process

[Mason Kramer via lldb-dev]

Thank you, Jan. --gdbserver-port was the flag I needed.

I also found that lldb-4.0 (packaged with Ubuntu 16.04) had another 
error with remote debugging that exhibited the same symptom. Upgrading 
lldb and setting --gdbserver-port were both required to remote debug my 
docker container. But now it works beautifully!

On 3/5/19 5:57 AM, Jan Kratochvil wrote:
> On Sun, 03 Mar 2019 04:17:42 +0100, Mason Kramer via lldb-dev wrote:
>> Then, I restricted the acceptable range of
>> gdbserver ports to just 5001, using the flags suggested in the email.
>>
>> lldb-server-4.0 platform --verbose --listen "*:5000" --min-gdbserver-port 5001 --max-gdbserver-port 5001
>                                                                                                        ^^^^
> There should be 5002 as --max-gdbserver-port is in reality "max+1" value and
> not "max" value.
>
> The options --min-gdbserver-port and --max-gdbserver-port get ignored this way.
>
> Submitted:
> 	Sanity check --max-gdbserver-port
> 	https://reviews.llvm.org/D58962
>
> Replied with a working Docker example:
> 	Remote LLDB debugging - Docker container
> 	https://stackoverflow.com/a/55004346/2995591
>
>
> # Add an option 'allow-all-hosts' to permit lldb debugging inside a Docker container
>> [2] https://reviews.llvm.org/D42845
> I also haven't found a need for this new proposed option.
>
>
> Jan
>