[drkonqi] [Bug 396893] New: drkonqi does not find kdbgwin located in the same directory
Ralf Habacker
bugzilla_noreply at kde.org
Fri Jul 27 00:24:55 BST 2018
https://bugs.kde.org/show_bug.cgi?id=396893
Bug ID: 396893
Summary: drkonqi does not find kdbgwin located in the same
directory
Product: drkonqi
Version: 5.13.3
Platform: Other
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: backtraceparsing
Assignee: unassigned-bugs at kde.org
Reporter: ralf.habacker at freenet.de
Target Milestone: ---
Just checked drkonqi crashtest application with a cross compiled drkonqi
package at
https://build.opensuse.org/package/show/home:rhabacker:branches:windows:mingw:win32:KF547/mingw32-drkonqi5
and got an issue that drkonqi.exe did not found kdbgwin.exe although it is
located in the same directory.
How to reproduce:
1. checkout package with
osc home:rhabacker:branches:windows:mingw:win32:KF547/mingw32-drkonqi5
2. build package with
cd home:rhabacker:branches:windows:mingw:win32:KF547/mingw32-drkonqi5
osc build openSUSE_Leap_42.3
3. copy crash test executable in standard binary dir to simulate a crashing
application
sudo cp
/var/tmp/build-root/openSUSE_Leap_42.3-x86_64/home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/build/crashtest.exe
/var/tmp/build-root/openSUSE_Leap_42.3-x86_64/usr/i686-w64-mingw32/sys-root/mingw/bin
4. setup a virtual machine with a least Windows 7 (32 or 64 bit)
5. share build folder e.g /var/tmp/build-root/ as L:
6. Open command shell at
L:\openSUSE_Leap_42.3\usr\i686-w64-mingw32\sys-root\mingw\bin [1]
7. run
L:\openSUSE_Leap_42.3-x86_64\home\abuild\rpmbuild\BUILD\drkonqi-5.13.3\build\bin\crashtest.exe
What happens ?
The message 'org.kde.drkonqi: Unable to find an internal debugger that can work
with the KCrash backend' is shown and no backtrace is available
Staying in [1] and adding '.' to PATH environment path variable fixes the
issue.
What is expected ?
Adding '.' to the windows system path is no option. Drkonqi should find kdbwin
without this explicit path settings
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list