https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #13 from Igor Kushnir ---
Found 3 similar backtraces in reported bugs for another KDE application and
Plasma: Bug 438541, Bug 491709, Bug 492634. Searched for "tzset" across KDE
projects via https://github.com/search?q=org%3AKDE+tzset&type=c
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #12 from Igor Kushnir ---
(In reply to Matthew Woehlke from comment #8)
> > Maybe a small program ...
>
> Alas, I don't think it's going to be that simple. I tried this:
A good sample program. I just tested it in Debug and Release and it ne
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #11 from Matthew Woehlke ---
Thread 732 (Thread 0x7fff33e006c0 (LWP 3923482) "Queue(0x576"):
#0 0x7fff6e54c420 in
L__N_119LValueExprEvaluatorEbJEE15VisitMemberExprEPKNS_10MemberExprE
(or_rangeIT_EE=0x7fff33df7378,
terDataDirectiveEP
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #10 from Matthew Woehlke ---
Thread 717 (Thread 0x7fff3cc006c0 (LWP 3923457) "Queue(0x576"):
#0 0x7fff6de9a8d2 in tuple_element<0UL, std::tuple > (InfoEv=0, *,
clang::IdentifierInfo *, clang::IdentifierInfo *, clang::IdentifierInfo
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #9 from Matthew Woehlke ---
Thread 715 (Thread 0x7fff4be006c0 (LWP 3923454) "Queue(0x576"):
#0 anonymous namespace)::ParameterStatus *, const (anonymous
namespace)::ParameterStatus *> (or_rangeIT_EE=,
StmtVisitorBaseISt11add_pointerN12_
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #8 from Matthew Woehlke ---
> Maybe a small program ...
Alas, I don't think it's going to be that simple. I tried this:
```
#include
#include
#include
QDateTime getMTime(QString const& path)
{
auto const fi = QFileInfo{path};
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #7 from Igor Kushnir ---
(In reply to Matthew Woehlke from comment #6)
> > Could you print the value of the local variable `localFile` at crash time?
>
> Which stack frame? The QFileInfo (#16) seems to be
> `Tests/RunCMake/Graphviz/set_grap
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #6 from Matthew Woehlke ---
> can you get us a `thread apply all bt`
Um... attempts to do so are causing gdb to go out to lunch for extended
periods...
That said, after a few runs I ran into a different failure mode, albeit one
that still
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #5 from Milian Wolff ---
Can you try to call `tzset()` once from the main thread somewhere, e.g. main?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #4 from Milian Wolff ---
can you get us a `thread apply all bt` - is this maybe some thread safety
problem that could be resolved by force-init'ing the code path once from the
main thread?
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=495261
Igor Kushnir changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
CC|
https://bugs.kde.org/show_bug.cgi?id=495261
Matthew Woehlke changed:
What|Removed |Added
Resolution|BACKTRACE |FIXED
--- Comment #2 from Matthew Woehlke --
https://bugs.kde.org/show_bug.cgi?id=495261
Milian Wolff changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=495261
Bug Janitor Service changed:
What|Removed |Added
Severity|normal |crash
--
You are receiving this mail bec
14 matches
Mail list logo
