[Bug 167911] New: drkonqi does not make backtraces of applications that are not in $PATH

[George Kiagiadakis]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=167911         
           Summary: drkonqi does not make backtraces of applications that
                    are not in $PATH
           Product: drkonqi
           Version: unspecified
          Platform: Debian testing
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs kde org
        ReportedBy: gkiagiad csd uoc gr


Version:            (using KDE 4.1.0)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc version 4.3.1 (Debian 4.3.1-2) 
OS:                Linux

I was wondering for a long time why drkonqi doesn't ever make backtraces of the applications that I develop myself, but it makes backtraces of kde applications... Today I did some research and found out that it makes backtraces only if the application that crashed lives in a directory in $PATH.

First I looked at the drkonqi code and found the hidden "developer mode" option, so I enabled it and then I had a "debugger" button in drkonqi. I made a simple test kde4 application that crashes and run it from my $HOME. It crashed, it opened drkonqi and I clicked the debugger button. This opened gdb in a konsole window, showing this:

GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(no debugging symbols found)
Attaching to program: /usr/bin/test, process 1157
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00007f52d6c8f210 in ?? ()
(gdb) bt
#0  0x00007f52d6c8f210 in ?? ()
#1  0x00007f52d6c8f064 in ?? ()
#2  0x00007f52d78159f0 in ?? ()
#3  0x0000000000000000 in ?? ()
(gdb)

Notice the "/usr/bin/test"! Remember that I ran this from my $HOME!
Then I looked in ps for the gdb command line and saw this:

 1163 pts/10   Ss+    0:00 /usr/bin/gdb -nw test 1157

This is obviously the wrong command line syntax. It could be far better if it had invoked gdb with this syntax: "gdb --pid 1157". This generates a correct backtrace here.

To double check this, I copied test to /usr/local/bin and then drkonqi was able to make a backtrace.