Bug 396893 - drkonqi does not find kdbgwin located in the same directory
Summary: drkonqi does not find kdbgwin located in the same directory
Status: RESOLVED WORKSFORME
Alias: None
Product: drkonqi
Classification: Applications
Component: backtraceparsing (show other bugs)
Version: 5.13.3
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks: 373980 380136
  Show dependency treegraph
 
Reported: 2018-07-26 23:24 UTC by Ralf Habacker
Modified: 2019-08-02 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Habacker 2018-07-26 23:24:55 UTC
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
Comment 1 Ralf Habacker 2018-07-26 23:26:18 UTC
(In reply to Ralf Habacker from comment #0)
> 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

Sorry - this need to be 
sudo cp /var/tmp/build-root/openSUSE_Leap_42.3-x86_64/home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/build/bin/crashtest.exe /var/tmp/build-root/openSUSE_Leap_42.3-x86_64/usr/i686-w64-mingw32/sys-root/mingw/bin
Comment 2 Harald Sitter 2019-06-18 15:35:49 UTC
Is this still valid with https://cgit.kde.org/drkonqi.git/commit/?id=8c74d90e28fb3474fe78ac449a49761f08dbd19f
Comment 3 Bug Janitor Service 2019-07-03 04:33:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Ralf Habacker 2019-07-03 05:47:11 UTC
(In reply to Harald Sitter from comment #2)
> Is this still valid with
> https://cgit.kde.org/drkonqi.git/commit/
> ?id=8c74d90e28fb3474fe78ac449a49761f08dbd19f

I can check that.
Comment 5 Bug Janitor Service 2019-07-18 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2019-08-02 04:33:11 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!