https://bugs.kde.org/show_bug.cgi?id=389413
Nikita Melnichenko changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=389413
Nikita Melnichenko changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #14 from Stefan Endrullis ---
That's it! You fixed the crash! Thank you very much!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
Nikita Melnichenko changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|UNCONFIR
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #12 from Stefan Endrullis ---
And thanks for your effort!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #11 from Stefan Endrullis ---
OK, waiting for more patches to test...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
Nikita Melnichenko changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #9 from Stefan Endrullis ---
OK, I checked out the new git master version, applied the patch, compiled and
started the project. Unfortunately, krusader crashed in the buggy directory
again:
#0 0x55711074 in memset (__len=295765780
https://bugs.kde.org/show_bug.cgi?id=389413
Nikita Melnichenko changed:
What|Removed |Added
Assignee|m...@fork.pl |nikita+...@melnichenko.name
--- Comment
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #7 from Stefan Endrullis ---
$ readlink -v core
readlink: core: Protocol error
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #6 from Nikita Melnichenko ---
Interesting. What does `readlink core` output?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #5 from Stefan Endrullis ---
OK, here is the backtrace with line numbers:
#0 0x55710ab5 in memset (__len=2957657807, __ch=0,
__dest=0x7fff4fb58670) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:71
#1 FileSystem::createL
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #4 from Nikita Melnichenko ---
Could you provide debug build backtrace which includes line numbers?
createLocalFileItem function is not small.
In addition, you can try one of the following approaches to repro locally:
https://unix.stackexch
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #3 from Stefan Endrullis ---
@Nikita
That's a good question. Unfortunately, I don't have an answer to it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
Nikita Melnichenko changed:
What|Removed |Added
CC||nikita+...@melnichenko.name
Resolu
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #1 from Stefan Endrullis ---
I completely forgot to mention the behavior of krusader.
So, krusader works fine as long as I do not enter directories with read errors,
but once I do it immediately crashes with an segmentation fault.
--
You
16 matches
Mail list logo
