Summary: | Crashed unmarking breakpoint | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Leozito <independent.scientist> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | 4.7.3 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | attachment-29698-0.html |
Description
Leozito
2016-05-20 20:55:14 UTC
Backtrace indicates this is an issue somewhere in the Qt modules; nothing we can do about. Is this crash reproducible? Created attachment 99106 [details] attachment-29698-0.html Yeah it looks like a Qt issue. Couldn't reproduce though. Thanks for the review! On Fri, May 20, 2016, 18:17 Kevin Funk via KDE Bugzilla < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=363341 > > Kevin Funk <kfunk@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution|--- |UPSTREAM > > --- Comment #1 from Kevin Funk <kfunk@kde.org> --- > Backtrace indicates this is an issue somewhere in the Qt modules; nothing > we > can do about. > > Is this crash reproducible? > > -- > You are receiving this mail because: > You reported the bug. > |