On May 29, 2008, at 20:58, Filipe Brandenburger wrote:
strace seems fine, just use some options to enhance the output you
get:
-s 1024: take 1024 bytes for every string. This wouldn't have cut
that one short
-tt: if you want timestamps
-f: to follow forked processes
I started strace with those parameters, but the strace output did not
change:
18:55:21 read(3, "\1\365\342\34\0\0\0\0\0\0\0\0\20\0\0\0\0\0\0\0\0\0\0
\0\20\0\0\0\234?\37\10", 32) = 32
18:55:21 write(3, "\0\0\2\0\1\0\1\0", 8) = 8
18:55:21 read(3, "\0\1\343\34\371\377?\3\0\0\0\0\1\0\0\0\0\0\0\0\10\0
\0\0\317U\t\10\0\0\0\0", 32) = 32
18:55:21 open("/usr/share/X11/XErrorDB", O_RDONLY) = 25
18:55:21 fstat64(25, {st_mode=S_IFREG|0644, st_size=37949, ...}) = 0
18:55:21 read(25, "! $Xorg: XErrorDB,v 1.3 2000/08/"..., 37949) = 37949
18:55:21 close(25) = 0
18:55:21 write(2, "The program \'gnome-terminal\' rec"..., 592) = 592
18:55:21 close(18) = 0
18:55:21 kill(26097, SIGTERM) = 0
18:55:21 writev(14, [{"GIOP\1\2\1\5\0\0\0\0", 12}], 1) = 12
18:55:21 close(14) = 0
18:55:21 writev(15, [{"GIOP\1\2\1\5\0\0\0\0", 12}], 1) = 12
18:55:21 close(15) = 0
18:55:21 writev(13, [{"GIOP\1\2\1\5\0\0\0\0", 12}], 1) = 12
18:55:21 close(13) = 0
18:55:21 writev(11, [{"GIOP\1\2\1\5\0\0\0\0", 12}], 1) = 12
18:55:21 close(11) = 0
18:55:21 close(9) = 0
18:55:21 close(8) = 0
18:55:21 unlink("/tmp/orbit-kb12698/linc-65ef-0-4ceb1113e5b63") = 0
18:55:21 close(12) = 0
18:55:21 exit_group(1) = ?
However, this time we started the gnome-terminal process from an
xterm, and here is what appeared on the screen after the crash:
** (gnome-terminal:26095): WARNING **: No handler for control
sequence `device-control-string' defined. [there were a bunch of
these lines, I think it happened before the crash]
The program 'gnome-terminal' 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 19864803 error_code 1 request_code 0 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.)
I will try to follow the instructions in the output to capture a
better error next time. I should probably also recompile gnome-
terminal with symbol information...
Alfred
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
