Bug 396915 - Incomplete backtrace from kdbgwin
Summary: Incomplete backtrace from kdbgwin
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 22:53 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 22:53:20 UTC
Running crashtest compiled for mingw returns: 


Application: crashtest (crashtest), signal: Unknown
crashtest.exe!SomeStruct::foo()() [/home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp @ 43] at 0x401925
crashtest.exe!__tmainCRTStartup() [/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c @ 336] at 0x4013eb
kernel32.dll!__tmainCRTStartup() [/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c @ 336] at 0x7712338a
ntdll.dll!__tmainCRTStartup() [/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c @ 336] at 0x77d79a02
ntdll.dll!__tmainCRTStartup() [/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c @ 336] at 0x77d799d5

Running the same application with 'gdb crashtest'

GNU gdb (GDB) 8.1
(gdb) r
Starting program: J:\openSUSE_Leap_42.3-x86_64\usr\i686-w64-mingw32\sys-root\mingw\bin\crashtest.exe
[New Thread 4892.0xaa4]
Program received signal SIGSEGV, Segmentation fault.
level4 (t=0) at /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp:104
104     /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp: No such file or directory.
(gdb) bt
#0  level4 (t=0) at /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp:104
#1  0x00408a55 in level3 (t=<optimized out>) at /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp:109
#2  level2 (t=<optimized out>) at /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp:114
#3  level1 (t=<optimized out>) at /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp:119
#4  main (argc=<optimized out>, argv=<optimized out>) at /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp:156
(gdb)

Comparing kdbgwin backtrace with the gdb backtrace shows that kdbgwin backtrace seems to be imcomplete.
Comment 1 Ralf Habacker 2018-07-30 06:37:19 UTC
Comparing the result from gb without debug symbols installed 

Thread 1 received signal SIGSEGV, Segmentation fault.
#0  0x0000000000401908 in ?? ()
#1  0x00000000004095a8 in ?? ()
#2  0x00000000004013f7 in ?? ()
#3  0x00000000004014fb in ?? ()
#4  0x00000000779559ed in KERNEL32!BaseThreadInitThunk () from C:\Windows\system32\kernel32.dll
#5  0x0000000077b8b371 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#6  0x0000000000000000 in ?? ()

with kdbgwin

kdbgwin
crashtest.exe!SomeStruct::foo()() [/home/abuild/rpmbuild/BUILD/kde-runtime-17.04.0.800ab1a/drkonqi/tests/crashtest/crashtest.cpp @ 43] at 0x401908
crashtest.exe!main() [/home/abuild/rpmbuild/BUILD/kde-runtime-17.04.0.800ab1a/drkonqi/tests/crashtest/crashtest.cpp @ 160] at 0x4095a8
crashtest.exe!__tmainCRTStartup() [/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c @ 336] at 0x4013f7
crashtest.exe!WinMainCRTStartup() [/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c @ 186] at 0x4014fb
kernel32.dll![unknown]() [[unknown] @ -1] at 0x779559ed
ntdll.dll![unknown]() [[unknown] @ -1] at 0x77b8b371

shows that the addresses are fetched correctly. The differences are in the source file and lines

gdb:     #0  level4 (t=0) at /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp:104
kdbgwin: crashtest.exe!SomeStruct::foo()() [/home/abuild/rpmbuild/BUILD/kde-runtime-17.04.0.800ab1a/drkonqi/tests/crashtest/crashtest.cpp @ 43] at 0x401908

gdb:     #1  0x00408a55 in level3 (t=<optimized out>) at /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp:109
kdbgwin: crashtest.exe!main() [/home/abuild/rpmbuild/BUILD/kde-runtime-17.04.0.800ab1a/drkonqi/tests/crashtest/crashtest.cpp @ 160] at 0x4095a8

gdb:     #2  level2 (t=<optimized out>) at /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp:114
kdbgwin: crashtest.exe!__tmainCRTStartup() [/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c @ 336] at 0x4013f7

gdb:     #3  level1 (t=<optimized out>) at /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest/crashtest.cpp:119
/crashtest.cpp:156
kdbgwin: crashtest.exe!WinMainCRTStartup() [/home/abuild/rpmbuild/BUILD/mingw-w64-crt/crt/crtexe.c @ 186] at 0x4014fb

gdb: #4  main (argc=<optimized out>, argv=<optimized out>) at /home/abuild/rpmbuild/BUILD/drkonqi-5.13.3/src/tests/crashtest
kdbgwin: kernel32.dll![unknown]() [[unknown] @ -1] at 0x779559ed
Comment 2 Justin Zobel 2023-01-19 00:19:01 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 3 Bug Janitor Service 2023-02-03 05:01:29 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 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!