https://bugs.kde.org/show_bug.cgi?id=509835

            Bug ID: 509835
           Summary: `drkonqi-6.4.4-1.fc42.x86_64` failed to `bt` with
                    `INTERNAL_SYSCALL_ERROR_P` when calling
                    `print_preamble_internal()` in
                    `/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.p
                    y`
    Classification: Applications
           Product: drkonqi
      Version First 6.4.4
       Reported In:
          Platform: Fedora RPMs
               URL: https://github.com/abrt/gnome-abrt/issues/392#issue-34
                    46024444
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: backtraceparsing
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Created attachment 185193
  --> https://bugs.kde.org/attachment.cgi?id=185193&action=edit
The Exported Failure Log

# SUMMARY

`plasma-drkonqi-6.4.4-1.fc42.x86_64.rpm` failed to generate a trace the first
time it attempted to.

# STEPS TO REPRODUCE

1. Induce
https://retrace.fedoraproject.org/faf/reports/bthash/30d842ce033b5a7db20734fd2361e4ec959273dd
of https://bugzilla.redhat.com/show_bug.cgi?id=2271266#c22, per
https://bugs.kde.org/show_bug.cgi?id=509834#c0.

2. Generate a backtrace.

3. When it fails, "Reload" it.

# OBSERVED RESULT

First, it fails:

> ~~~
> Core was generated by `/usr/bin/plasmashell --no-respawn'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  __pthread_kill_implementation (threadid=<optimized out>, 
> signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
> 44          return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO 
> (ret) : 0;
> [Current thread is 1 (Thread 0x7f3b0686a300 (LWP 2315))]
> KCRASH_INFO_MESSAGE: Content of s_kcrashErrorMessage: std::unique_ptr<char 
> []> = {get() = <optimized out>}
> 
> Cannot QML trace cores :(
> Traceback (most recent call last):
>   File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 812, in 
> print_preamble
>     print_preamble_internal()
>     ~~~~~~~~~~~~~~~~~~~~~~~^^
>   File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 803, in 
> print_preamble_internal
>     print_sentry_payload(thread)
>     ~~~~~~~~~~~~~~~~~~~~^^^^^^^^
>   File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 727, in 
> print_sentry_payload
>     payload = SentryEvent().make(program, thread)
>   File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 520, in 
> make
>     stacktrace = SentryTrace(crash_thread, True).to_dict()
>   File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 369, in 
> to_dict
>     frames = [ SentryFrame(frame) for frame in 
> gdb.FrameIterator.FrameIterator(gdb.newest_frame()) ]
>                                                
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
>   File "/usr/share/gdb/python/gdb/FrameIterator.py", line 42, in __next__
>     self.frame = result.older()
>                  ~~~~~~~~~~~~^^
> gdb.error: could not read '.gnu_debugaltlink' section
> could not read '.gnu_debugaltlink' section
> Sentry is attempting to send 2 pending events
> Waiting up to 30 seconds
> Press Ctrl-C to quit
> Debugging ended with exit code '1' and exit status 'NormalExit'
> ~~~

Afterward, it succeeds.

# EXPECTED RESULT

It should always generate a trace.

# SOFTWARE/OS VERSIONS

> ~~~
> Operating System: Fedora Linux 42
> KDE Plasma Version: 6.4.4
> KDE Frameworks Version: 6.17.0
> Qt Version: 6.9.2
> Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit)
> Memory: 32 GiB of RAM (30.4 GiB usable)
> ~~~

# ADDITIONAL INFORMATION

- This appears most similar to the error logs in
https://bugs.kde.org/show_bug.cgi?id=507143#c0:~:text=return-,INTERNAL_SYSCALL_ERROR_P,-(ret)%20?%20INTERNAL_SYSCALL_ERRNO,
except that what https://bugs.kde.org/show_bug.cgi?id=507143#c1 describes
cannot have occurred.

- Considering that
https://github.com/abrt/gnome-abrt/issues/392#issue-3446024444 also occurred,
this might relate to it.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to