Graham Inggs wrote:
On 7 June 2014 18:17, Waxhead <waxh...@online.no> wrote:
Hi Graham,
Not that often. However it still happens.... I have also changed graphics cards
(and drivers) from GeForce 8600 and 7300 to one single 660 card in case it
might be valuable info.
Also just for the record doublecmd sometimes (again not often) "crash to
oblivion" e.g. just quits when changing directories / closing tabs etc...
I mostly access files over a nfs4 share, but it seem to happen "randomly" on
other directories as well. Also from my gut feeling it seems to happen more often after a
hibernate, but this is just speculation.
If it is of any value I will from now on run doublecmd with "gdb doublecmd" and
do a backtrace whenever something weird happens. If there is something I can do to give
you the best possible data please let me know (I know C if that helps).
- Svein
Yes, please attach a backtrace to this bug report the next time it happens.
Hi again (I hope this helps somehow...). happened when changing
directories (on a NFS share)
The program 'doublecmd' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this
connection)'.
(Details: serial 5616406 error_code 14 request_code 55 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
[Thread 0x7fffc3de9700 (LWP 10526) exited]
[Thread 0x7fffe0c14700 (LWP 10505) exited]
[Thread 0x7fffe10fd700 (LWP 10504) exited]
[Thread 0x7fffe14fe700 (LWP 10503) exited]
[Thread 0x7fffe1b46700 (LWP 10502) exited]
[Thread 0x7fffe1f47700 (LWP 10501) exited]
[Thread 0x7fffe2b51700 (LWP 10500) exited]
[Thread 0x7fffef9d4700 (LWP 10499) exited]
[Thread 0x7ffff7fb7980 (LWP 10494) exited]
[Inferior 1 (process 10494) exited with code 01]
(gdb) backtrace
No stack.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
