[Bug 1585928] [NEW] [SRU] llvm-defaults 0.33ubuntu4 [was: lldb package does not provide a lldb-server symlink to the current default version]

Launchpad Bug Tracker 1585928 at bugs.launchpad.net
Thu Jun 16 07:50:56 UTC 2016


You have been subscribed to a public bug by Jan Henke (jhe):

[Impact]

 * The lldb package in xenial provides a unversioned symlink only for
the lldb-3.8 executable from the lldb-3.8 package, but not for the lldb-
server-3.8, lldb-argdumper-3.8 and lldb-mi-3.8 binaries

* It breaks lldb's ability to run an executable inside the debugger

* It breaks user expectation as the other three binaries cannot be
invoked by the unversioned name

[Test Case]

 * Start a debugging session for any application with `lldb <path to
executable>

* On the lldb prompt enter `run`

* Expected result: The application is run inside the debugger
* Actual result: The debugger cannot launch the application, because it cannot find the `lldb-server` component of lldb

[Regression Potential]

 * None, the bugfix adds unversioned symlinks for the rest of the
executables from the lldb-3.8 package, which were missing before. It
should not affect the behaviour of any other application on the system.

[Other Info]
 
 * This is a very simple patch by just adding three more symlinks in the packaging.

[Original Bug Description]

The lldb package provides a symlink to the current default version of
lldb, so that the command lldb works as an alias to the real executable
lldb-3.8.

Please also provide a similar symlink for the lldb-server executable.
The current lldb-3.8 package already provides the executable with the
name lldb-server-3.8.

** Affects: llvm-defaults (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: llvm-defaults (Ubuntu Xenial)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug xenial
-- 
[SRU] llvm-defaults 0.33ubuntu4 [was: lldb package does not provide a lldb-server symlink to the current default version]
https://bugs.launchpad.net/bugs/1585928
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list