It helps a little, Gilberto; now we know that your binary has no debugging
symbols, so the backtrace would be of minimal use to us :-( . If you have
free time or a desire how to learn how these things work, you could try
compiling XEmacs, and repeating the attempt. “bt” is the short version of
the GDB command “backtrace”; you need to type it within GDB, not at the
shell prompt.
Ar an seachtú lá déag de mí Iúil, scríobh Gilberto:
Does this it help? I can find a program call "bt", I am
running on a Ubuntu
machine and I am just a little bit more than a basic linux user. It looks to
be something related to the graphics not being properly defined through the
session.
gdb /usr/bin/xemacs core
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<
http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(no debugging symbols found)
/home/gilberto/cctv/tools/sw/ltib-imx27ads-20071219/rpm/BUILD/misc/test/mxc_
vpu_test/core: No such file or directory.
(gdb) run
Starting program: /usr/bin/xemacs
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x7f7ea99606e0 (LWP 28952)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
Warning: Color name "Black" is not defined
Warning: Color name "Gray80" is not defined
Warning: Cannot convert string
"-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string
"-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*,
-*-*-*-*-*-*-*-120-*-iso10646-1,
-*-*-*-*-*-*-*-120-*-jisx0208.1983-0,
-*-*-*-*-*-*-*-120-*-jisx0201.1976-0" to type FontSet
Warning: Missing charsets in String to FontSet conversion
Warning: Color name "Gray30" is not defined
Warning: Color name "Blue" is not defined
Warning: Color name "Red" is not defined
Warning: Color name "Maroon" is not defined
Warning: Color name "ForestGreen" is not defined
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f7ea99606e0 (LWP 28952)]
0x0000000000563b50 in ?? ()
-----Original Message-----
From: Aidan Kehoe [mailto:kehoea@parhasard.net]
Sent: viernes, 17 de julio de 2009 11:57
To: Gilberto
Cc: xemacs-beta(a)xemacs.org
Subject: Re: Problem report.
Ar an séú lá déag de mí Iúil, scríobh Gilberto:
> Starting Xemacs through a NXclient sesion reports this problem:
>
> Lisp backtrace follows:
>
> # bind (frame-being-created)
> make-frame(nil #<x-device on "localhost:11.0" 0xb1e>)
> frame-initialize()
> # bind (debugger debug-on-error command-line-args-left)
> command-line()
> # (condition-case ... . ((t (byte-code " \ufffd\ufffd" ... 1))))
> # bind (error-data)
> normal-top-level()
> # (condition-case ... . error)
> # (catch top-level ...)
>
> [1] Segmentation fault xemacs vpu_codec.c
Thanks, Gilberto! We can’t really do anything with that without a C
backtrace (though I suppose we could research what NXclient is and try to
reproduce it); could you attempt the same thing within GDB, and send us the
C backtrace (type bt once the program has crashed) ?
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta