Rbx at 0x7fffffffd368, rbp at 0x7fffffffd370, rip at 0x7fffffffd378 Locals at 0x7fffffffd360, Previous frame's sp is 0x7fffffffd380 I hope the Xfce team can solve this soon, because I have to sort out some old backed-up directories and I'm used to using thunar to do this sort of work! I don't know if it helps at all, but I used gdb to print some extra info from the last stack frame reached in thunar. ![]() I also cannot rename files without thunar going away on me. I have a similar or identical backtrace to the one posted in the original bug report. I wonder what makes my system different it crash so often.Ĭomment 9 Dave Witbrodt 06:06:52 CET (In reply to Harald Judt from comment #1) There has to be another test if file_a->collate_key or file_a->collate_key are NULL. The problem is that THUNAR_IS_FILE returns true (for file_a and file_b), but pointers to collate_key are NULL. > can apply, but until we have a good solution it could help. > Does the attached workaround prevent the crashes? It is not a proper fix we I also noticed that sometimes, when I rename file, there appears second file with the same name like the first one (checked it with "ls -l" - there is only one real file). It can be the reason why running Thunar with gdb has about 10 times less crashes. > the old file is in the process of being destroyed while being compared with > needs to be protected to avoid being accessed when it shouldn't be. > This is probably related to threading issues and timing-specific. > is not called, but when it is (it is random), then it crashes. > working directory - both file_a->collate_key_nocase and > thunar_file_compare_by_name() function is called even for only one file in > gdb backtrace attached - it is strange that the ![]() > check-thunar-file-instance-when-comparing-filenames.patch (In reply to Harald Judt from comment #1)
0 Comments
Leave a Reply. |