[Trisquel-devel] dino-im segfaulting on Trisquel GNU/Linux 12.0

[Xavier Del Campo Romero]

Hi Bill,

Thank you for the quick reply. Find attached the complete (gzipped) 
backtrace as a text file.

Having another look at this issue, I can see pango_language_get_default 
was not to blame, but still |pango_font_default_has_char is passing a 
null pointer to ||pango_coverage_get without null pointer checks.|

I have also uploaded the (gzipped) core file into my web server:

https://slcl.privatedns.org/public/b0a324c64bd97e1bc4c8e2b0d1067f9b

Thank you again for your help.

Best regards,

Xavi

On 25/5/25 21:20, bill-auger wrote:
> On Sun, 25 May 2025 20:49:57 +0200 Xavier wrote:
>> (gdb) bt
>> #0  pango_coverage_get (coverage=0x0, index=84) at ../pango/pango-coverage.c:183
>> #1  0x00007ffff6db44fc in pango_font_default_has_char (font=<optimized out>, wc=84) at ../pango/fonts.c:1795
> it would be helpful to show the complete un-edited back-trace - that incomplete
> back-trace suggests that pango is not the problem - pango (stack frame #0 and
> #1) has received a NULL from its caller (not shown) - more likely, the NULL
> originates from the client (dino?) and may be evident in the lower stack frames
>
> the fact that it is choking on a font definition may suggest that the client
> expects some specific font to be installed that is not installed (ie: the
> client package has an undeclared dependency on some font package)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bt.txt.gz
Type: application/gzip
Size: 1739 bytes
Desc: not available
URL: <http://listas.trisquel.info/pipermail/trisquel-devel/attachments/20250525/71b844c7/attachment.gz>