GNOME.org
 

Crash trying to use OTF

Hello all,
I'm posting this crash log here since I don't know where to send it. When trying to select the font I finished developing for the Mandombe script, in any gnome application, it crashes.The problem occurs everytime I try to select it. However, viewing pdf generated under OSX with the same font doesn't cause any trouble. 
Tnks

#######################################################
From:  <>
To: submit bugs gnome org
X-Mailer: bug-buddy 2.12.1
Subject: crash when attempting to use specific otf font

Distribution: Ubuntu 5.10 (breezy)
Package: gucharmap
Severity: Normal
Version: GNOME2.12.1 1.4.4
Gnome-Distributor: Ubuntu
Synopsis: crash when attempting to use specific otf font
Bugzilla-Product: gucharmap
Bugzilla-Component: general
Bugzilla-Version: 1.4.4
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. install mandombe fonts
2. run any gnome application
3. select the font

Expected Results:

correct rendering of the font
How often does this happen?
everytime

Additional Information:
otf font developed by myself with fontlab4.6 for a Mandombe script.


Debugging Information:

Backtrace was generated from '/usr/bin/gucharmap'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(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)
(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]
[New Thread -1227126048 (LWP 8950)]
(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)
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb704f483 in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7b7b508 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3  <signal handler called>
#4  0xb75a752d in FcFreeTypeCharIndex () from
/usr/lib/libfontconfig.so.1
#5  0xb7691132 in pango_fc_font_create_metrics_for_context ()
   from /usr/lib/libpangoft2-1.0.so.0
#6  0xb76912d0 in pango_fc_font_get_glyph ()
   from /usr/lib/libpangoft2-1.0.so.0
#7  0xb6b7ee11 in ?? () from
/usr/lib/pango/1.4.0/modules/pango-basic-fc.so
#8  0x08274610 in ?? ()
#9  0x00010300 in ?? ()
#10 0xb6ef79e4 in malloc_trim () from /lib/tls/i686/cmov/libc.so.6
#11 0xb7640be7 in pango_engine_shape_get_type ()
   from /usr/lib/libpango-1.0.so.0
#12 0xb764fa09 in pango_shape () from /usr/lib/libpango-1.0.so.0
#13 0xb76443e4 in pango_layout_set_width () from
/usr/lib/libpango-1.0.so.0
#14 0xb764671b in pango_layout_iter_get_char_extents ()
   from /usr/lib/libpango-1.0.so.0
#15 0xb7646f78 in pango_layout_iter_get_char_extents ()
   from /usr/lib/libpango-1.0.so.0
#16 0xb76478a7 in pango_layout_iter_get_char_extents ()
   from /usr/lib/libpango-1.0.so.0
#17 0xb764873a in pango_layout_get_pixel_size ()
   from /usr/lib/libpango-1.0.so.0
#18 0xb7c98946 in gucharmap_table_get_active_character ()
   from /usr/lib/libgucharmap.so.4
#19 0xb7c98d83 in gucharmap_table_get_active_character ()
   from /usr/lib/libgucharmap.so.4
#20 0xb7c9937e in gucharmap_table_redraw () from
/usr/lib/libgucharmap.so.4
#21 0xb788402c in _gtk_marshal_BOOLEAN__BOXED ()
   from /usr/lib/libgtk-x11-2.0.so.0
#22 0xb708c3a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#23 0xb709ab13 in g_signal_stop_emission () from
/usr/lib/libgobject-2.0.so.0
#24 0xb709bec3 in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#25 0xb709c4c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#26 0xb796616f in gtk_widget_activate () from
/usr/lib/libgtk-x11-2.0.so.0
#27 0xb7882d72 in gtk_main_do_event () from
/usr/lib/libgtk-x11-2.0.so.0
#28 0xb7713bfa in gdk_window_clear_area_e () from
/usr/lib/libgdk-x11-2.0.so.0
#29 0xb7713ccd in gdk_window_process_all_updates ()
   from /usr/lib/libgdk-x11-2.0.so.0
#30 0xb77fa6c5 in gtk_container_check_resize ()
   from /usr/lib/libgtk-x11-2.0.so.0
#31 0xb6fe9750 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
#32 0xb6fe74ee in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#33 0xb6fea4f6 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#34 0xb6fea7e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#35 0xb7881e65 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#36 0x0804927c in main ()

Thread 1 (Thread -1227126048 (LWP 8950)):
#0  0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb704f483 in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#2  0xb7b7b508 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
No symbol table info available.
#3  <signal handler called>
No symbol table info available.
#4  0xb75a752d in FcFreeTypeCharIndex () from
/usr/lib/libfontconfig.so.1
No symbol table info available.
#5  0xb7691132 in pango_fc_font_create_metrics_for_context ()
   from /usr/lib/libpangoft2-1.0.so.0
No symbol table info available.
#6  0xb76912d0 in pango_fc_font_get_glyph ()
   from /usr/lib/libpangoft2-1.0.so.0
No symbol table info available.
#7  0xb6b7ee11 in ?? () from
/usr/lib/pango/1.4.0/modules/pango-basic-fc.so
No symbol table info available.
#8  0x08274610 in ?? ()
No symbol table info available.
#9  0x00010300 in ?? ()
No symbol table info available.
#10 0xb6ef79e4 in malloc_trim () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#11 0xb7640be7 in pango_engine_shape_get_type ()
   from /usr/lib/libpango-1.0.so.0
No symbol table info available.
#12 0xb764fa09 in pango_shape () from /usr/lib/libpango-1.0.so.0
No symbol table info available.
#13 0xb76443e4 in pango_layout_set_width () from
/usr/lib/libpango-1.0.so.0
No symbol table info available.
#14 0xb764671b in pango_layout_iter_get_char_extents ()
   from /usr/lib/libpango-1.0.so.0
No symbol table info available.
#15 0xb7646f78 in pango_layout_iter_get_char_extents ()
   from /usr/lib/libpango-1.0.so.0
No symbol table info available.
#16 0xb76478a7 in pango_layout_iter_get_char_extents ()
   from /usr/lib/libpango-1.0.so.0
No symbol table info available.
#17 0xb764873a in pango_layout_get_pixel_size ()
   from /usr/lib/libpango-1.0.so.0
No symbol table info available.
#18 0xb7c98946 in gucharmap_table_get_active_character ()
   from /usr/lib/libgucharmap.so.4
No symbol table info available.
#19 0xb7c98d83 in gucharmap_table_get_active_character ()
   from /usr/lib/libgucharmap.so.4
No symbol table info available.
#20 0xb7c9937e in gucharmap_table_redraw () from
/usr/lib/libgucharmap.so.4
No symbol table info available.
#21 0xb788402c in _gtk_marshal_BOOLEAN__BOXED ()
   from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#22 0xb708c3a8 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#23 0xb709ab13 in g_signal_stop_emission () from
/usr/lib/libgobject-2.0.so.0
No symbol table info available.
#24 0xb709bec3 in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
No symbol table info available.
#25 0xb709c4c3 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#26 0xb796616f in gtk_widget_activate () from
/usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#27 0xb7882d72 in gtk_main_do_event () from
/usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#28 0xb7713bfa in gdk_window_clear_area_e () from
/usr/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#29 0xb7713ccd in gdk_window_process_all_updates ()
   from /usr/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#30 0xb77fa6c5 in gtk_container_check_resize ()
   from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#31 0xb6fe9750 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#32 0xb6fe74ee in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
No symbol table info available.
#33 0xb6fea4f6 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
No symbol table info available.
#34 0xb6fea7e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#35 0xb7881e65 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#36 0x0804927c in main ()
No symbol table info available.
#0  0xffffe410 in __kernel_vsyscall ()
################################################

Le 13 avr. 06, à 18:00, gtk-i18n-list-request gnome org a écrit :


Send gtk-i18n-list mailing list submissions to
	gtk-i18n-list gnome org

To subscribe or unsubscribe via the World Wide Web, visit
	http://mail.gnome.org/mailman/listinfo/gtk-i18n-list
or, via email, send a message with subject or body 'help' to
	gtk-i18n-list-request gnome org

You can reach the person managing the list at
	gtk-i18n-list-owner gnome org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gtk-i18n-list digest..."


Today's Topics:

   1. Re: Extending pango markup (Kalle Vahlman)
   2. Re: Extending pango markup (Behdad Esfahbod)
   3. Re: Extending pango markup (Behdad Esfahbod)


----------------------------------------------------------------------

Message: 1
Date: Wed, 12 Apr 2006 21:25:59 +0300
From: "Kalle Vahlman" <kalle vahlman gmail com>
Subject: Re: Extending pango markup
To: "Behdad Esfahbod" <behdad cs toronto edu>
Cc: gtk-i18n-list gnome org
Message-ID:
	<177e83dd0604121125r6bafb15evecb5a75916df9f05 mail gmail com>
Content-Type: text/plain; charset=UTF-8

(finally got time to continue this...)

On 4/9/06, Behdad Esfahbod <behdad cs toronto edu> wrote:

Hi,

I certainly don't like the way your patch works.


Given that it indeed was the quick-and-dirty hack to see if it would
be feasible at all, I'd hate you if you _did_ like it. ;)


 What I like
instead is a way to get/set GMarkup markup-parser and data on
your PangoLayout.  Then you can get the current parser and data,
embed them into your own data, and set your own parser and data
that will fallback to Pango's parser/data for tags it doesn't
like...


Hmm, not sure if I get this right but wouldn't this be almost like
repimplementing the whole markup parsing in every application with the
only convenience being the parsing of existing tags (so you'd have to
keep track of the indexes etc. yourself)?


This should let you do what you want, but doesn't allow
implementing arbitrary markup parsers, as it doesn't expose the
MarkupData struct (and it really shouldn't.)


I agree here.


 Another approach is
to go one step further and make the markup-parser paroperty take
a function with similar signature as pango_parse_markup and data
so you don't even have to use GMarkup (and GMarkup is not in the
Pango API currently.)  But then you cannot do what you currently
want to do.  Something in between should be possible, I'm not
sure.


Basically what I'm looking for is a way to say to pango "if this tag
is present when you parse the markup, please ask me if I want to apply
attributes to that location".

What about having an "unkown tag" callback to a
pango_parse_markup()-sibling that would simply give the tag name and
attributes as parameter to the callback and that callback would return
a list of attributes to be applied for the enclosed text? Possibly
you'd want a user data parameter too there...

My concern with full-featured parsing support is that it easily gets
too heavy to use when compared to some lazy hacking (and we all know
what people are like when doing it Right gets too complicated... ;).

--
Kalle Vahlman, zuh iki fi
Powered by http://movial.fi
Interesting stuff at http://syslog.movial.fi

------------------------------

Message: 2
Date: Thu, 13 Apr 2006 04:10:15 -0400 (EDT)
From: Behdad Esfahbod <behdad cs toronto edu>
Subject: Re: Extending pango markup
To: zuh iki fi
Cc: gtk-i18n-list gnome org
Message-ID: <Pine LNX 4 58 0604130349310 7946 epoch cs>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 12 Apr 2006, Kalle Vahlman wrote:


instead is a way to get/set GMarkup markup-parser and data on
your PangoLayout.  Then you can get the current parser and data,
embed them into your own data, and set your own parser and data
that will fallback to Pango's parser/data for tags it doesn't
like...


Hmm, not sure if I get this right but wouldn't this be almost like
repimplementing the whole markup parsing in every application with the
only convenience being the parsing of existing tags (so you'd have to
keep track of the indexes etc. yourself)?


Yes, exactly.  So rule this off.



 Another approach is
to go one step further and make the markup-parser paroperty take
a function with similar signature as pango_parse_markup and data
so you don't even have to use GMarkup (and GMarkup is not in the
Pango API currently.)  But then you cannot do what you currently
want to do.  Something in between should be possible, I'm not
sure.


Basically what I'm looking for is a way to say to pango "if this tag
is present when you parse the markup, please ask me if I want to apply
attributes to that location".


Ok, I guess so, but you didn't say in your original post that you
want to emit pango attributes in your tags, so I was not sure.



What about having an "unkown tag" callback to a
pango_parse_markup()-sibling that would simply give the tag name and
attributes as parameter to the callback and that callback would return
a list of attributes to be applied for the enclosed text? Possibly
you'd want a user data parameter too there...


Yeah, that's almost what I have in mind now.  I was thinking more
about having a hashtable mapping new tags to callbacks, but that
is not even easier to use, so one callback is probably the
easiest.  It takes the tag, XML attribute name/values,
current Pango attributes (not sure if this last one is a good
idea / really needed.  do you happen to need them?), and a
GError, and one of 1) returns one attribute (flawed), 2) returns
a list of attributes (a bit more pain than 1, but more generic),
or 3) prepends the new attributes to the input list and return
the new list.  Option 2 is probably the cleanest, while 3 is
easiest to use...  Not sure here.


My concern with full-featured parsing support is that it easily gets
too heavy to use when compared to some lazy hacking (and we all know
what people are like when doing it Right gets too complicated... ;).


Yes agreed.  I on the other hand, prefer to address the problem
more generally now that we are adding API for this.  For example,
it should allow for turning off the internal set of attributes
IMO, so you can write parsers for arbitrary markups.

Some not-quite-unrelated discussion is going on in bug 330960:

  http://bugzilla.gnome.org/show_bug.cgi?id=330960

Although with this new approach, it seems to be quite unrelated
now :).


Ok, I think you should file this as a bug and we can continue
there.


behdad


------------------------------

Message: 3
Date: Thu, 13 Apr 2006 04:11:14 -0400 (EDT)
From: Behdad Esfahbod <behdad cs toronto edu>
Subject: Re: Extending pango markup
To: zuh iki fi
Cc: gtk-i18n-list gnome org
Message-ID: <Pine LNX 4 58 0604130410240 7946 epoch cs>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 13 Apr 2006, Behdad Esfahbod wrote:


Some not-quite-unrelated discussion is going on in bug 330960:

  http://bugzilla.gnome.org/show_bug.cgi?id=330960



Oops Oops Oops Oops.  Meant bug #337518:

  http://bugzilla.gnome.org/show_bug.cgi?id=337518


behdad


------------------------------

_______________________________________________
gtk-i18n-list mailing list
gtk-i18n-list gnome org
http://mail.gnome.org/mailman/listinfo/gtk-i18n-list


End of gtk-i18n-list Digest, Vol 24, Issue 8
********************************************
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]