Kubuntu Flight 5: Cannot backtrace in Crash Handler

[tmp]

Upon a crash I select "Backtrace" in the KDE Crash Handler but then get the following error message:
  "Could not generate backtrace as the debugger 'gdb' was not found"

[Dennis Kaarsemaker (dennis)]

launchpad auto-person-search-thing sucks...

[Kenny Duffus (kduffus)]

gdb is not part of the standard install

[Graeme Hewson (ghewson)]

Quite, gdb *should* be part of the standard install, at least for alpha/beta releases. I'd have saved a fair amount of time in my testing of Flight 5 if gdb had been installed already (it wasn't a simple matter in my case to download it after the install from CD).

[tmp (skrald)]

Generally: If some functionality will not work unless some ressource is installed, then there should be no link (or similiar) to that functionality.

More specificly: If gdb is not installed in the default installation, then the backtrace tab should not be displayed at all (as it wouldn't work anyway).

[Graeme Hewson (ghewson)]

I disagree with the above comment. It probably wouldn't have occurred to me to install gdb if the tab hadn't been displayed. Perhaps the tab should be greyed out, but that could be confusing too.

[Brian Ealdwine (eode)]

The tab's page could be replaced with a page that says "A necessary utility for backtracing is not installed. If you would like to help trace future problems, click the 'install gdb' button in order to install this utility." <install gdb>.

..this makes it easy for the user to make that choice, without requiring additional initial install.

[Sarah Kowalik (hobbsee-deactivatedaccount)]

Can we get gdb on the cd? the dependancies dont look too massive, and gdb is already in main.

[Andrew Ash (ash211)]

gdb was released on the edgy final cd, so backtracing should work correctly