It turns out there is gdb magic that finds everything it needs to
describe symbols and variables in /usr/src/debug, which is populated
by first setting enabled=1 in the updates-newkey-debuginfo section /
etc/yum.repo.d/fedora-updates-newkey.repo and then doing "sudo yum
install tk-debuginfo". After pursuing my problem, I found that the
weird font name made available by my X11 server of "-misc-????-bold-r-
normal--0-0-0-0-p-0-iso8859-1" was causing the problem; I've submitted
a patch to both tcl.sourceforge.net and bugzilla.redhat.com to return
TCL_ERROR from the TkParseFontXLFD function instead of a structure
containing a NULL pointer where the font family is expected to be.
- Stephen
On Nov 5, 3:04 pm, "Ville M. Vainio" <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 5, 2008 at 9:56 PM, thyrsus <[EMAIL PROTECTED]> wrote:
> > others. Leo is only a victim in this scenario, but could someone
> > point me to a tutorial on Fedora/RHEL debugging procedures? E.g.,
>
> I suppose the debugging procedure is like it's elsewhere... compile
> own version of libtk to /usr/local/lib with debug symbols, ensure that
> it get used, and run it in gdb (or analyze the coredump with gdb).
>
> --
> Ville M. Vainiohttp://tinyurl.com/vainio
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
