Bug 396916 - drkonqi could not parse kdbgwin output on Windows/Mingw
Summary: drkonqi could not parse kdbgwin output on Windows/Mingw
Status: RESOLVED WORKSFORME
Alias: None
Product: drkonqi
Classification: Applications
Component: general (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-27 23:14 UTC by Ralf Habacker
Modified: 2023-02-18 03:47 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Habacker 2018-07-27 23:14:22 UTC
Running crash test app from drkonqi build returns:

KCrash: Application 'crashtest.exe' crashing...
org.kde.drkonqi: Executable is: "J:/openSUSE_Leap_42.3-x86_64/usr/i686-w64-mingw32/sys-root/mingw/bin/crashtest.exe"
org.kde.drkonqi: Executable exists: true
org.kde.drkonqi: Enabling drkonqi crash catching
kf5.kwidgetsaddons: Invalid pixmap specified.
org.kde.drkonqi.parser: line "crashtest.exe!SomeStruct::foo()() [/home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp @ 43] at 0x401925\n" did not match
org.kde.drkonqi.parser: "__tmainCRTStartup" "/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c" "crashtest.exe"
org.kde.drkonqi.parser: "__tmainCRTStartup" "/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c" "kernel32.dll"
org.kde.drkonqi.parser: "__tmainCRTStartup" "/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c" "ntdll.dll"
org.kde.drkonqi.parser: "__tmainCRTStartup" "/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c" "ntdll.dll"
org.kde.drkonqi.parser: line "" did not match
org.kde.drkonqi.parser: Rating: 0 out of 0 Usefulness: Useless
org.kde.drkonqi.parser: 90%: 0 70%: 0 40%: 0
org.kde.drkonqi.parser: Have seen stack base: false Lines counted: 0

How to reproduce:
Follow howto at https://bugs.kde.org/show_bug.cgi?id=396893#c0
Comment 1 Justin Zobel 2023-01-19 00:18:50 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2023-02-03 05:01:30 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 3 Bug Janitor Service 2023-02-18 03:47:32 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!