https://bugs.kde.org/show_bug.cgi?id=454411
BEEDELL ROKE JULIAN LOCKHART <beedellrokejulianlockh...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO |RESOLVED
--- Comment #3 from BEEDELL ROKE JULIAN LOCKHART
<beedellrokejulianlockh...@gmail.com> ---
(In reply to BEEDELL ROKE JULIAN LOCKHART from comment #2)
> (In reply to Harald Sitter from comment #1)
> > Cannot reproduce. When gdb is missing the output isn't that it crashed and
> > when I install it and click the reload button it correctly creates a trace.
> > What am I missing?
> >
> > Is your problem reproducible at all? You can force any application to crash
> > by running `killall -SEGV kwrite` or some other name.
>
> You shall need to wait some time before I am able to potentially reproduce
> this again, because DrKonqi was recently rewritten in Kirigami, and updates
> to Fedora may have remediated this, and I shall need to configure a new
> system without GDB and cause an error that DrKonqi notices to evaluate
> whether this continues to occur.
Sorry. I didn't read your comment at all. It works now.
--
You are receiving this mail because:
You are watching all bug changes.
