texmacs-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Texmacs-dev] Experimental Qt port


From: Joris van der Hoeven
Subject: Re: [Texmacs-dev] Experimental Qt port
Date: Tue, 30 Sep 2008 09:40:41 +0200
User-agent: Mutt/1.5.9i

On Tue, Sep 30, 2008 at 01:25:57AM -0500, Juan Pablo Romero Méndez wrote:
> Now it compiles with just one change:
> 
> in src/Plugins/Qt/QTMGuiHelper.hpp
> 
> line 45:
> 
> virtual int QTMStyle::pixelMetric(PixelMetric metric, const
> QStyleOption *opt, const QWidget *widget) const;
> 
> 
> gcc 4.2.1 requires:
> 
> virtual int pixelMetric(PixelMetric metric, const QStyleOption *opt,
> const QWidget *widget) const;
> 
> 
> The problem is in execution; it seg faults with any keystroke.
> 
> I've tried debugging it, but I'm not sure how. I tried launching "gdb
> texmacs.bin procID"
> 
> this is the result of "bt":
> 
> (gdb) r
> The program being debugged has been started already.
> Start it from the beginning? (y or n) y
> Starting program:
> /home/jpablo/extra/texmacs-cvs/libexec/TeXmacs/bin/texmacs.bin
> (no debugging symbols found)
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb6efb9b0 (LWP 12021)]
> TeXmacs] couldn't concretize ? (none)
> TeXmacs] couldn't concretize ? (none)
> TeXmacs] couldn't concretize ? (concat, xxx, ? (concat, fonts, type1))
> TeXmacs] couldn't concretize ? (concat, xxx, ? (concat, fonts, type1))
> 
> TeXmacs]
> TeXmacs] Installation problem: please send a bug report.
> TeXmacs] The initialization file init-texmacs.scm could not be found.
> TeXmacs] Please check the values of the environment variables
> TeXmacs] TEXMACS_PATH and GUILE_LOAD_PATH. init-texmacs.scm should
> TeXmacs] be readable and in the directory $TEXMACS_PATH/progs
> TeXmacs] or in the directory $GUILE_LOAD_PATH
> TeXmacs]
> 
> Fatal error: Guile could not be found in 'init_guile'
> See file   : init_texmacs.cpp
> 
> Program received signal SIGABRT, Aborted.
> [Switching to Thread 0xb6efb9b0 (LWP 12021)]
> 0xffffe410 in __kernel_vsyscall ()
> (gdb) bt
> #0  0xffffe410 in __kernel_vsyscall ()
> #1  0xb70568f5 in raise () from /lib/libc.so.6
> #2  0xb70581e1 in abort () from /lib/libc.so.6
> #3  0x08421b85 in FT_Select_Charmap ()
> #4  0x085ba300 in ?? ()
> #5  0x085950fd in ?? ()
> #6  0x00000001 in ?? ()
> #7  0xbfccac7c in ?? ()
> #8  0x00000018 in ?? ()
> #9  0x00000018 in ?? ()
> #10 0x0000000a in ?? ()
> #11 0x0841fdb0 in FT_Select_Charmap ()
> #12 0x00000020 in ?? ()
> #13 0x0863bc01 in ?? ()
> #14 0x705ba300 in ?? ()
> #15 0xbfccac7c in ?? ()
> #16 0xbfccac78 in ?? ()
> #17 0xbfccac74 in ?? ()
> #18 0xbfccac98 in ?? ()
> #19 0x083237d8 in FT_Select_Charmap ()
> #20 0xbfccac7c in ?? ()
> #21 0xbfccac78 in ?? ()
> #22 0xbfccac74 in ?? ()
> #23 0xbfccac68 in ?? ()
> #24 0xb7095179 in free () from /lib/libc.so.6
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> (gdb)

Please configure with --enable-debug (in addition to --enable-qt of course)
when providing a backtrace.

Best wishes, Joris




reply via email to

[Prev in Thread] Current Thread [Next in Thread]