open-discussion
open-discussion > RE: error:gdkERROR **: The program 'MRIcroGL' rec
May 14, 2015 05:05 AM | wolf bill
RE: error:gdkERROR **: The program 'MRIcroGL' rec
No,I just run MricroGL,
compute-0-1 mricrontab]$ ./MRIcroGL
Gdk-ERROR **: The program 'MRIcroGL' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 2147 error_code 1 request_code 150 minor_code 168)
(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.)
aborting...
Aborted
When I run it with --sync I still get the same error:
ompute-0-1 mricrontab]$ ./MRIcroGL --sync
Gdk-ERROR **: The program 'MRIcroGL' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 4350 error_code 1 request_code 150 minor_code 168)
(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.)
aborting...
Aborted
compute-0-1 mricrontab]$ ./MRIcroGL
Gdk-ERROR **: The program 'MRIcroGL' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 2147 error_code 1 request_code 150 minor_code 168)
(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.)
aborting...
Aborted
When I run it with --sync I still get the same error:
ompute-0-1 mricrontab]$ ./MRIcroGL --sync
Gdk-ERROR **: The program 'MRIcroGL' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 4350 error_code 1 request_code 150 minor_code 168)
(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.)
aborting...
Aborted
Threaded View
| Title | Author | Date |
|---|---|---|
| wolf bill | May 14, 2015 | |
| vsochat | May 14, 2015 | |
| wolf bill | May 14, 2015 | |
| Erika Nixon | Jun 8, 2015 | |
