Don't like ads? PRO users don't see any ads ;-)
Guest

Untitled

By: a guest on Nov 23rd, 2010  |  syntax: None  |  size: 1.96 KB  |  hits: 19  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. john@satellite ~ $ gdb gae_g3dviewer
  2. GNU gdb (GDB) 7.2-ubuntu
  3. Copyright (C) 2010 Free Software Foundation, Inc.
  4. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  5. This is free software: you are free to change and redistribute it.
  6. There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  7. and "show warranty" for details.
  8. This GDB was configured as "i686-linux-gnu".
  9. For bug reporting instructions, please see:
  10. <http://www.gnu.org/software/gdb/bugs/>...
  11. Reading symbols from /usr/local/bin/gae_g3dviewer...(no debugging symbols found)...done.
  12. (gdb) r
  13. Starting program: /usr/local/bin/gae_g3dviewer
  14. [Thread debugging using libthread_db enabled]
  15. The program 'gae_g3dviewer' received an X Window System error.
  16. This probably reflects a bug in the program.
  17. The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  18.   (Details: serial 336 error_code 9 request_code 137 minor_code 8)
  19.   (Note to programmers: normally, X errors are reported asynchronously;
  20.    that is, you will receive the error a while after causing it.
  21.    To debug your program, run it with the --sync command line
  22.    option to change this behavior. You can then get a meaningful
  23.    backtrace from your debugger if you break on the gdk_x_error() function.)
  24.  
  25. Program exited with code 01.
  26. (gdb) bt
  27. No stack.
  28. (gdb) q
  29. john@satellite ~ $ gae_g3dviewer --sync
  30. The program 'gae_g3dviewer' received an X Window System error.
  31. This probably reflects a bug in the program.
  32. The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  33.   (Details: serial 747 error_code 9 request_code 137 minor_code 8)
  34.   (Note to programmers: normally, X errors are reported asynchronously;
  35.    that is, you will receive the error a while after causing it.
  36.    To debug your program, run it with the --sync command line
  37.    option to change this behavior. You can then get a meaningful
  38.    backtrace from your debugger if you break on the gdk_x_error() function.)
  39. john@satellite ~ $