https://bugs.kde.org/show_bug.cgi?id=356174
Bug ID: 356174
Summary: Enhance the embedded gdbserver to allow LLDB to use it
Product: valgrind
Version: 3.10.0
Platform: unspecified
OS: All
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: dtrebb...@gmail.com
Because Mac OS X no longer ships with gdb, it would be useful to allow LLDB's
support for gdb-remote debugging to be used with the embedded gdbserver.
Reproducible: Always
Steps to Reproduce:
On a Mac system:
1. Install Homebrew's valgrind package.
2. In one terminal, start valgrind with --vgdb-error=0:
valgrind --vgdb-error=0 ./myprogram
3. In another terminal, start LLDB:
lldb ./myprogram
4. In another terminal, start vgdb listening on an unused port (e.g. port
12851):
vgdb --port=12851
5. In the LLDB terminal, run the gdb-remote command to connect:
(lldb) gdb-remote 12851
6. Try to continue by running 'c' in LLDB:
(lldb) c
Actual Results:
LLDB will display "error: Process must be launched." because it thinks that the
./myprogram process has not been started.
Expected Results:
Running 'c' in LLDB after connecting should continue execution of the program
and LLDB should be usable to debug.
I am using:
- valgrind-3.11.0
- Mac OS X 10.11.1 'El Capitan'
- lldb-340.4.110.1
--
You are receiving this mail because:
You are watching all bug changes.
