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

--- Comment #5 from Roke Julian Lockhart Beedell 
<[email protected]> ---
Created attachment 183232
  --> https://bugs.kde.org/attachment.cgi?id=183232&action=edit
A Consistent Reproduction Screencast

(In reply to Roke Julian Lockhart Beedell from comment #4)

> In that case, it shouldn't ask the user to retry in the Developer Mode,
> and shouldn't endlessly pretend to submit it in the Automatic mode,
> and should actually explain the problem.

I've since ascertained that I can reproducibly invoke this by opening a large
file in Okular or KWrite, then closing it when it hangs (basically, by doing
what https://bugs.kde.org/show_bug.cgi?id=507036 describes in anything except
Ark):

> ~~~
> Starting debugger gdb --init-eval-command=set auto-solib-add off --nw --nx 
> --batch --init-eval-command=set debuginfod enabled on 
> --command=/tmp/drkonqi.eMxFSl --command=/tmp/drkonqi.hLYdUw 
> --core=/tmp/drkonqi-core.DNsffL/core /usr/bin/kwrite
> Downloading 447.07 K separate debug info for /usr/bin/kwrite...
> Downloading 4.70 M separate debug info for 
> /home/RokeJulianLockhart/.cache/debuginfod_client/b925112a06f58dad79498eabb93272c2e5083586/debuginfo...
> 
> warning: BFD: warning: /tmp/drkonqi-core.DNsffL/core has a segment extending 
> past end of file
> 
> warning: Can't open file /memfd:wayland-shm (deleted) during file-backed 
> mapping note processing
> [New LWP 22142]
> [New LWP 22148]
> [New LWP 22147]
> [New LWP 22145]
> [New LWP 22143]
> [New LWP 22160]
> [New LWP 22150]
> [New LWP 22152]
> [New LWP 22161]
> [New LWP 22146]
> [New LWP 22153]
> [New LWP 22151]
> [New LWP 22149]
> [New LWP 22164]
> [New LWP 22177]
> [New LWP 22165]
> [New LWP 22178]
> [New LWP 22163]
> [New LWP 22162]
> 
> warning: failed to parse execution context from corefile: Cannot access 
> memory at address 0x7ffd3e081fe8
> 
> warning: Error reading shared library list entry at 0x723a565200343932
> Cannot access memory at address 0x6e613a564200313a
> Cannot access memory at address 0x6e613a5642003132
> Failed to read a valid object file image from memory.
> Core was generated by `/usr/bin/kwrite 
> /home/RokeJulianLockhart/Downloads/official-cpe-dictionary_v2.3'.
> Program terminated with signal SIGABRT, Aborted.
> #0  0x00007f2a40a8111c in ?? ()
> [Current thread is 1 (LWP 22142)]
> 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 367, in 
> to_dict
>     SentryTrace.load_solib(self.thread, cramped_memory)
>     ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   File "/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py", line 332, in 
> load_solib
>     raise UnexpectedMappingException(f"No solib and no image found for frame 
> #{i} on thread {thread}! You could try with debug symbols downloading 
> enabled.")
> UnexpectedMappingException: No solib and no image found for frame #0 on 
> thread <gdb.InferiorThread id=1.1 target-id="LWP 22142">! You could try with 
> debug symbols downloading enabled.
> No solib and no image found for frame #0 on thread <gdb.InferiorThread id=1.1 
> target-id="LWP 22142">! You could try with debug symbols downloading enabled.
> 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'
> ~~~

Considering that this seems like a somewhat common outcome, perhaps it should
be better handled.

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

Reply via email to