public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* segfault in xwin-xdg-menu.exe
@ 2018-05-11 15:38 Fabio Rossi
  2018-05-11 15:54 ` Marco Atzeri
  2018-05-11 17:25 ` Ken Brown
  0 siblings, 2 replies; 9+ messages in thread
From: Fabio Rossi @ 2018-05-11 15:38 UTC (permalink / raw)
  To: cygwin

I have just made a fresh cygwin installation on windows 10 pro 32bit using setup 2.891. I have selected xorg-server, xinit, vim and gdb packages. I have modified the Xwin server configuration as described in https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-startxwinrc-exit and later I have successfully started it by using the action "cygwin-x\xwin server" under Windows programs menu. The X server is running with display :0.0 and its icon is visible in the tray bar.

On another system installed months ago I have the xdg menu application already running (it's automatically started by the xwin startup script) but I didn't need to follow the above mentioned trick described in the FAQ.

In a cygwin terminal I then try starting manually xwin-xdg-menu by using:

$ DISPLAY=:0 xwin-xdg-menu.exe

but I get a segmentation fault. With gdb I get the following backtrace:

$ DISPLAY=:0 gdb xwin-xdg-menu.exe

GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
Copyright (C) 2015 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 "i686-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from xwin-xdg-menu.exe...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/xwin-xdg-menu.exe
[New Thread 6888.0x1578]
[New Thread 6888.0xecc]
[New Thread 6888.0x404]
[New Thread 6888.0x1bdc]
[New Thread 6888.0x6f4]
[New Thread 6888.0xdd4]
[New Thread 6888.0x1b04]
[New Thread 6888.0xf38]

Program received signal SIGSEGV, Segmentation fault.
0x6d0af8f0 in cygfontconfig-1!FcFreeTypeQueryFace () from /usr/bin/cygfontconfig-1.dll
(gdb) bt
#0  0x6d0af8f0 in cygfontconfig-1!FcFreeTypeQueryFace () from /usr/bin/cygfontconfig-1.dll
#1  0x6d0ab98b in cygfontconfig-1!FcFileScanConfig () from /usr/bin/cygfontconfig-1.dll
#2  0x6d0abd59 in cygfontconfig-1!FcFileScanConfig () from /usr/bin/cygfontconfig-1.dll
#3  0x6d0abfb6 in cygfontconfig-1!FcDirCacheScan () from /usr/bin/cygfontconfig-1.dll
#4  0x6d0a762c in cygfontconfig-1!FcConfigAddCache () from /usr/bin/cygfontconfig-1.dll
#5  0x6d0a76d6 in cygfontconfig-1!FcConfigBuildFonts () from /usr/bin/cygfontconfig-1.dll
#6  0x6d0b0cce in cygfontconfig-1!FcInitLoadOwnConfigAndFonts () from /usr/bin/cygfontconfig-1.dll
#7  0x6d0b0cff in cygfontconfig-1!FcInitLoadConfigAndFonts () from /usr/bin/cygfontconfig-1.dll
#8  0x6d0a4845 in cygfontconfig-1!FcConfigDestroy () from /usr/bin/cygfontconfig-1.dll
#9  0x6d0a63ce in cygfontconfig-1!FcConfigSubstituteWithPat () from /usr/bin/cygfontconfig-1.dll
#10 0x6d0a6d97 in cygfontconfig-1!FcConfigSubstitute () from /usr/bin/cygfontconfig-1.dll
#11 0x6c0a5cc5 in pango_cairo_fc_font_get_type () from /usr/bin/cygpangocairo-1.0-0.dll
#12 0x6c084c87 in pango_fc_font_get_raw_extents () from /usr/bin/cygpangoft2-1.0-0.dll
#13 0x6c0cc090 in pango_color_parse () from /usr/bin/cygpango-1.0-0.dll
#14 0x6c0cd68a in pango_itemize_with_base_dir () from /usr/bin/cygpango-1.0-0.dll
#15 0x6c0d5c89 in pango_layout_line_get_extents () from /usr/bin/cygpango-1.0-0.dll
#16 0x6c0d7c72 in pango_layout_move_cursor_visually () from /usr/bin/cygpango-1.0-0.dll
#17 0x6c0d8204 in pango_layout_get_size () from /usr/bin/cygpango-1.0-0.dll
#18 0x6b8bd65a in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
#19 0x6b8bd569 in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
#20 0x6b8bd936 in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
#21 0x6b8b742c in rsvg_new_ellipse () from /usr/bin/cygrsvg-2-2.dll
#22 0x6b8b78ad in rsvg_new_ellipse () from /usr/bin/cygrsvg-2-2.dll
#23 0x6b8b8332 in rsvg_node_draw () from /usr/bin/cygrsvg-2-2.dll
#24 0x6b8c5834 in rsvg_handle_render_cairo_sub () from /usr/bin/cygrsvg-2-2.dll
#25 0x6b8c600f in rsvg_handle_get_pixbuf_sub () from /usr/bin/cygrsvg-2-2.dll
#26 0x6b8c60a7 in rsvg_handle_get_pixbuf () from /usr/bin/cygrsvg-2-2.dll
#27 0x6a5112e9 in ?? () from /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/cygpixbufloader-svg.dll
#28 0x6cb89918 in gdk_pixbuf_loader_close () from /usr/bin/cyggdk_pixbuf-2.0-0.dll
#29 0x6cb8620c in gdk_pixbuf_format_copy () from /usr/bin/cyggdk_pixbuf-2.0-0.dll
#30 0x6cb871cb in gdk_pixbuf_new_from_stream_at_scale () from /usr/bin/cyggdk_pixbuf-2.0-0.dll
#31 0x6bbae43d in gtk_icon_info_free () from /usr/bin/cyggtk-x11-2.0-0.dll
#32 0x6bbb169c in gtk_icon_info_load_icon () from /usr/bin/cyggtk-x11-2.0-0.dll
#33 0x00401eee in ?? ()
#34 0x004023ce in ?? ()
#35 0x0040249f in ?? ()
#36 0x004025fb in ?? ()
#37 0x00403bf3 in ?? ()
#38 0x61007a27 in cygwin_exit_return () from /usr/bin/cygwin1.dll
#39 0x00000001 in ?? ()
#40 0x0068cc6c in ?? ()
#41 0x610056c2 in _cygtls::call2(unsigned long (*)(void*, void*), void*, void*) () from /usr/bin/cygwin1.dll
(gdb)

It seems a problem with fontconfig. Any hint?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: segfault in xwin-xdg-menu.exe
  2018-05-11 15:38 segfault in xwin-xdg-menu.exe Fabio Rossi
@ 2018-05-11 15:54 ` Marco Atzeri
  2018-05-11 16:26   ` Fabio Rossi
  2018-05-11 17:25 ` Ken Brown
  1 sibling, 1 reply; 9+ messages in thread
From: Marco Atzeri @ 2018-05-11 15:54 UTC (permalink / raw)
  To: cygwin

On 5/11/2018 5:29 PM, Fabio Rossi wrote:
> I have just made a fresh cygwin installation on windows 10 pro 32bit using setup 2.891. I have selected xorg-server, xinit, vim and gdb packages. I have modified the Xwin server configuration as described in https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-startxwinrc-exit and later I have successfully started it by using the action "cygwin-x\xwin server" under Windows programs menu. The X server is running with display :0.0 and its icon is visible in the tray bar.
> 
> On another system installed months ago I have the xdg menu application already running (it's automatically started by the xwin startup script) but I didn't need to follow the above mentioned trick described in the FAQ.
> 
> In a cygwin terminal I then try starting manually xwin-xdg-menu by using:
> 
> $ DISPLAY=:0 xwin-xdg-menu.exe
> 
> but I get a segmentation fault. With gdb I get the following backtrace:
> 
> $ DISPLAY=:0 gdb xwin-xdg-menu.exe
> 
...

> 
> It seems a problem with fontconfig. Any hint?
> 
> --

as suggested here

> Problem reports:       http://cygwin.com/problems.html

provide the cygcheck.out as attachment

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: segfault in xwin-xdg-menu.exe
  2018-05-11 15:54 ` Marco Atzeri
@ 2018-05-11 16:26   ` Fabio Rossi
  2018-05-11 16:46     ` Marco Atzeri
  0 siblings, 1 reply; 9+ messages in thread
From: Fabio Rossi @ 2018-05-11 16:26 UTC (permalink / raw)
  To: cygwin, Marco Atzeri

[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]

> Il 11 maggio 2018 alle 17.37 Marco Atzeri <marco.atzeri@gmail.com> ha scritto:
> 
> On 5/11/2018 5:29 PM, Fabio Rossi wrote:
> 
> > I have just made a fresh cygwin installation on windows 10 pro 32bit using setup 2.891. I have selected xorg-server, xinit, vim and gdb packages. I have modified the Xwin server configuration as described in https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-startxwinrc-exit and later I have successfully started it by using the action "cygwin-x\xwin server" under Windows programs menu. The X server is running with display :0.0 and its icon is visible in the tray bar.
> > 
> > On another system installed months ago I have the xdg menu application already running (it's automatically started by the xwin startup script) but I didn't need to follow the above mentioned trick described in the FAQ.
> > 
> > In a cygwin terminal I then try starting manually xwin-xdg-menu by using:
> > 
> > $ DISPLAY=:0 xwin-xdg-menu.exe
> > 
> > but I get a segmentation fault. With gdb I get the following backtrace:
> > 
> > $ DISPLAY=:0 gdb xwin-xdg-menu.exe
> > 
> > ...
> > 
> > It seems a problem with fontconfig. Any hint?
> > 
> > --
> 
> as suggested here
> 
> > Problem reports: http://cygwin.com/problems.html
> 
> provide the cygcheck.out as attachment

I missed that, sorry, here is the file attached as requested

[-- Attachment #2: cygcheck.out --]
[-- Type: chemical/x-gulp, Size: 31771 bytes --]

[-- Attachment #3: Type: text/plain, Size: 219 bytes --]


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: segfault in xwin-xdg-menu.exe
  2018-05-11 16:26   ` Fabio Rossi
@ 2018-05-11 16:46     ` Marco Atzeri
  0 siblings, 0 replies; 9+ messages in thread
From: Marco Atzeri @ 2018-05-11 16:46 UTC (permalink / raw)
  To: Fabio Rossi, cygwin

On 5/11/2018 5:54 PM, Fabio Rossi wrote:
>> Il 11 maggio 2018 alle 17.37 Marco Atzeri ha scritto:
>>

>>> In a cygwin terminal I then try starting manually xwin-xdg-menu by using:
>>>
>>> $ DISPLAY=:0 xwin-xdg-menu.exe
>>>
>>> but I get a segmentation fault. With gdb I get the following backtrace:
>>>
>>> $ DISPLAY=:0 gdb xwin-xdg-menu.exe
>>>
>>> ...
>>>
>>> It seems a problem with fontconfig. Any hint?
>>>
>>> --
>>
>> as suggested here
>>
>>> Problem reports: http://cygwin.com/problems.html
>>
>> provide the cygcheck.out as attachment
> 
> I missed that, sorry, here is the file attached as requested
> 

I do not see any obvious issue, sorry.
May be xwin-xdg-menu needs need a font you don't have

Try with strace to see what is trying to do/open before the segfault

DISPLAY=:0 strace -o /tmp/xwin-xdg-menu.strace /usr/bin/xwin-xdg-menu.exe



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: segfault in xwin-xdg-menu.exe
  2018-05-11 15:38 segfault in xwin-xdg-menu.exe Fabio Rossi
  2018-05-11 15:54 ` Marco Atzeri
@ 2018-05-11 17:25 ` Ken Brown
  2018-05-11 20:28   ` Fabio Rossi
  1 sibling, 1 reply; 9+ messages in thread
From: Ken Brown @ 2018-05-11 17:25 UTC (permalink / raw)
  To: cygwin

On 5/11/2018 11:29 AM, Fabio Rossi wrote:
> I have just made a fresh cygwin installation on windows 10 pro 32bit using setup 2.891. I have selected xorg-server, xinit, vim and gdb packages. I have modified the Xwin server configuration as described in https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-startxwinrc-exit and later I have successfully started it by using the action "cygwin-x\xwin server" under Windows programs menu. The X server is running with display :0.0 and its icon is visible in the tray bar.
> 
> On another system installed months ago I have the xdg menu application already running (it's automatically started by the xwin startup script) but I didn't need to follow the above mentioned trick described in the FAQ.
> 
> In a cygwin terminal I then try starting manually xwin-xdg-menu by using:
> 
> $ DISPLAY=:0 xwin-xdg-menu.exe
> 
> but I get a segmentation fault. With gdb I get the following backtrace:
> 
> $ DISPLAY=:0 gdb xwin-xdg-menu.exe
> 
> GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
> Copyright (C) 2015 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 "i686-pc-cygwin".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from xwin-xdg-menu.exe...(no debugging symbols found)...done.
> (gdb) run
> Starting program: /usr/bin/xwin-xdg-menu.exe
> [New Thread 6888.0x1578]
> [New Thread 6888.0xecc]
> [New Thread 6888.0x404]
> [New Thread 6888.0x1bdc]
> [New Thread 6888.0x6f4]
> [New Thread 6888.0xdd4]
> [New Thread 6888.0x1b04]
> [New Thread 6888.0xf38]
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x6d0af8f0 in cygfontconfig-1!FcFreeTypeQueryFace () from /usr/bin/cygfontconfig-1.dll
> (gdb) bt
> #0  0x6d0af8f0 in cygfontconfig-1!FcFreeTypeQueryFace () from /usr/bin/cygfontconfig-1.dll
> #1  0x6d0ab98b in cygfontconfig-1!FcFileScanConfig () from /usr/bin/cygfontconfig-1.dll
> #2  0x6d0abd59 in cygfontconfig-1!FcFileScanConfig () from /usr/bin/cygfontconfig-1.dll
> #3  0x6d0abfb6 in cygfontconfig-1!FcDirCacheScan () from /usr/bin/cygfontconfig-1.dll
> #4  0x6d0a762c in cygfontconfig-1!FcConfigAddCache () from /usr/bin/cygfontconfig-1.dll
> #5  0x6d0a76d6 in cygfontconfig-1!FcConfigBuildFonts () from /usr/bin/cygfontconfig-1.dll
> #6  0x6d0b0cce in cygfontconfig-1!FcInitLoadOwnConfigAndFonts () from /usr/bin/cygfontconfig-1.dll
> #7  0x6d0b0cff in cygfontconfig-1!FcInitLoadConfigAndFonts () from /usr/bin/cygfontconfig-1.dll
> #8  0x6d0a4845 in cygfontconfig-1!FcConfigDestroy () from /usr/bin/cygfontconfig-1.dll
> #9  0x6d0a63ce in cygfontconfig-1!FcConfigSubstituteWithPat () from /usr/bin/cygfontconfig-1.dll
> #10 0x6d0a6d97 in cygfontconfig-1!FcConfigSubstitute () from /usr/bin/cygfontconfig-1.dll
> #11 0x6c0a5cc5 in pango_cairo_fc_font_get_type () from /usr/bin/cygpangocairo-1.0-0.dll
> #12 0x6c084c87 in pango_fc_font_get_raw_extents () from /usr/bin/cygpangoft2-1.0-0.dll
> #13 0x6c0cc090 in pango_color_parse () from /usr/bin/cygpango-1.0-0.dll
> #14 0x6c0cd68a in pango_itemize_with_base_dir () from /usr/bin/cygpango-1.0-0.dll
> #15 0x6c0d5c89 in pango_layout_line_get_extents () from /usr/bin/cygpango-1.0-0.dll
> #16 0x6c0d7c72 in pango_layout_move_cursor_visually () from /usr/bin/cygpango-1.0-0.dll
> #17 0x6c0d8204 in pango_layout_get_size () from /usr/bin/cygpango-1.0-0.dll
> #18 0x6b8bd65a in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
> #19 0x6b8bd569 in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
> #20 0x6b8bd936 in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
> #21 0x6b8b742c in rsvg_new_ellipse () from /usr/bin/cygrsvg-2-2.dll
> #22 0x6b8b78ad in rsvg_new_ellipse () from /usr/bin/cygrsvg-2-2.dll
> #23 0x6b8b8332 in rsvg_node_draw () from /usr/bin/cygrsvg-2-2.dll
> #24 0x6b8c5834 in rsvg_handle_render_cairo_sub () from /usr/bin/cygrsvg-2-2.dll
> #25 0x6b8c600f in rsvg_handle_get_pixbuf_sub () from /usr/bin/cygrsvg-2-2.dll
> #26 0x6b8c60a7 in rsvg_handle_get_pixbuf () from /usr/bin/cygrsvg-2-2.dll
> #27 0x6a5112e9 in ?? () from /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/cygpixbufloader-svg.dll
> #28 0x6cb89918 in gdk_pixbuf_loader_close () from /usr/bin/cyggdk_pixbuf-2.0-0.dll
> #29 0x6cb8620c in gdk_pixbuf_format_copy () from /usr/bin/cyggdk_pixbuf-2.0-0.dll
> #30 0x6cb871cb in gdk_pixbuf_new_from_stream_at_scale () from /usr/bin/cyggdk_pixbuf-2.0-0.dll
> #31 0x6bbae43d in gtk_icon_info_free () from /usr/bin/cyggtk-x11-2.0-0.dll
> #32 0x6bbb169c in gtk_icon_info_load_icon () from /usr/bin/cyggtk-x11-2.0-0.dll
> #33 0x00401eee in ?? ()
> #34 0x004023ce in ?? ()
> #35 0x0040249f in ?? ()
> #36 0x004025fb in ?? ()
> #37 0x00403bf3 in ?? ()
> #38 0x61007a27 in cygwin_exit_return () from /usr/bin/cygwin1.dll
> #39 0x00000001 in ?? ()
> #40 0x0068cc6c in ?? ()
> #41 0x610056c2 in _cygtls::call2(unsigned long (*)(void*, void*), void*, void*) () from /usr/bin/cygwin1.dll
> (gdb)
> 
> It seems a problem with fontconfig. Any hint?

Could it be the same problem as this?

   https://cygwin.com/ml/cygwin/2018-04/msg00325.html

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: segfault in xwin-xdg-menu.exe
  2018-05-11 17:25 ` Ken Brown
@ 2018-05-11 20:28   ` Fabio Rossi
  2018-05-12 14:43     ` Jon Turney
  0 siblings, 1 reply; 9+ messages in thread
From: Fabio Rossi @ 2018-05-11 20:28 UTC (permalink / raw)
  To: cygwin, Ken Brown

> Il 11 maggio 2018 alle 19.12 Ken Brown <kbrown@cornell.edu> ha scritto:
> 
> On 5/11/2018 11:29 AM, Fabio Rossi wrote:
> 
> > I have just made a fresh cygwin installation on windows 10 pro 32bit using setup 2.891. I have selected xorg-server, xinit, vim and gdb packages. I have modified the Xwin server configuration as described in https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-startxwinrc-exit and later I have successfully started it by using the action "cygwin-x\xwin server" under Windows programs menu. The X server is running with display :0.0 and its icon is visible in the tray bar.
> > 
> > On another system installed months ago I have the xdg menu application already running (it's automatically started by the xwin startup script) but I didn't need to follow the above mentioned trick described in the FAQ.
> > 
> > In a cygwin terminal I then try starting manually xwin-xdg-menu by using:
> > 
> > $ DISPLAY=:0 xwin-xdg-menu.exe
> > 
> > but I get a segmentation fault. With gdb I get the following backtrace:
> > 
> > $ DISPLAY=:0 gdb xwin-xdg-menu.exe
> > 
> > GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
> > Copyright (C) 2015 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 "i686-pc-cygwin".
> > Type "show configuration" for configuration details.
> > For bug reporting instructions, please see:
> > <http://www.gnu.org/software/gdb/bugs/>.
> > Find the GDB manual and other documentation resources online at:
> > <http://www.gnu.org/software/gdb/documentation/>.
> > For help, type "help".
> > Type "apropos word" to search for commands related to "word"...
> > Reading symbols from xwin-xdg-menu.exe...(no debugging symbols found)...done.
> > (gdb) run
> > Starting program: /usr/bin/xwin-xdg-menu.exe
> > [New Thread 6888.0x1578]
> > [New Thread 6888.0xecc]
> > [New Thread 6888.0x404]
> > [New Thread 6888.0x1bdc]
> > [New Thread 6888.0x6f4]
> > [New Thread 6888.0xdd4]
> > [New Thread 6888.0x1b04]
> > [New Thread 6888.0xf38]
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x6d0af8f0 in cygfontconfig-1!FcFreeTypeQueryFace () from /usr/bin/cygfontconfig-1.dll
> > (gdb) bt
> > 
> > #0 0x6d0af8f0 in cygfontconfig-1!FcFreeTypeQueryFace () from /usr/bin/cygfontconfig-1.dll
> > 
> > #1 0x6d0ab98b in cygfontconfig-1!FcFileScanConfig () from /usr/bin/cygfontconfig-1.dll
> > 
> > #2 0x6d0abd59 in cygfontconfig-1!FcFileScanConfig () from /usr/bin/cygfontconfig-1.dll
> > 
> > #3 0x6d0abfb6 in cygfontconfig-1!FcDirCacheScan () from /usr/bin/cygfontconfig-1.dll
> > 
> > #4 0x6d0a762c in cygfontconfig-1!FcConfigAddCache () from /usr/bin/cygfontconfig-1.dll
> > 
> > #5 0x6d0a76d6 in cygfontconfig-1!FcConfigBuildFonts () from /usr/bin/cygfontconfig-1.dll
> > 
> > #6 0x6d0b0cce in cygfontconfig-1!FcInitLoadOwnConfigAndFonts () from /usr/bin/cygfontconfig-1.dll
> > 
> > #7 0x6d0b0cff in cygfontconfig-1!FcInitLoadConfigAndFonts () from /usr/bin/cygfontconfig-1.dll
> > 
> > #8 0x6d0a4845 in cygfontconfig-1!FcConfigDestroy () from /usr/bin/cygfontconfig-1.dll
> > 
> > #9 0x6d0a63ce in cygfontconfig-1!FcConfigSubstituteWithPat () from /usr/bin/cygfontconfig-1.dll
> > 
> > #10 0x6d0a6d97 in cygfontconfig-1!FcConfigSubstitute () from /usr/bin/cygfontconfig-1.dll
> > 
> > #11 0x6c0a5cc5 in pango_cairo_fc_font_get_type () from /usr/bin/cygpangocairo-1.0-0.dll
> > 
> > #12 0x6c084c87 in pango_fc_font_get_raw_extents () from /usr/bin/cygpangoft2-1.0-0.dll
> > 
> > #13 0x6c0cc090 in pango_color_parse () from /usr/bin/cygpango-1.0-0.dll
> > 
> > #14 0x6c0cd68a in pango_itemize_with_base_dir () from /usr/bin/cygpango-1.0-0.dll
> > 
> > #15 0x6c0d5c89 in pango_layout_line_get_extents () from /usr/bin/cygpango-1.0-0.dll
> > 
> > #16 0x6c0d7c72 in pango_layout_move_cursor_visually () from /usr/bin/cygpango-1.0-0.dll
> > 
> > #17 0x6c0d8204 in pango_layout_get_size () from /usr/bin/cygpango-1.0-0.dll
> > 
> > #18 0x6b8bd65a in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
> > 
> > #19 0x6b8bd569 in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
> > 
> > #20 0x6b8bd936 in rsvg_state_reconstruct () from /usr/bin/cygrsvg-2-2.dll
> > 
> > #21 0x6b8b742c in rsvg_new_ellipse () from /usr/bin/cygrsvg-2-2.dll
> > 
> > #22 0x6b8b78ad in rsvg_new_ellipse () from /usr/bin/cygrsvg-2-2.dll
> > 
> > #23 0x6b8b8332 in rsvg_node_draw () from /usr/bin/cygrsvg-2-2.dll
> > 
> > #24 0x6b8c5834 in rsvg_handle_render_cairo_sub () from /usr/bin/cygrsvg-2-2.dll
> > 
> > #25 0x6b8c600f in rsvg_handle_get_pixbuf_sub () from /usr/bin/cygrsvg-2-2.dll
> > 
> > #26 0x6b8c60a7 in rsvg_handle_get_pixbuf () from /usr/bin/cygrsvg-2-2.dll
> > 
> > #27 0x6a5112e9 in ?? () from /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/cygpixbufloader-svg.dll
> > 
> > #28 0x6cb89918 in gdk_pixbuf_loader_close () from /usr/bin/cyggdk_pixbuf-2.0-0.dll
> > 
> > #29 0x6cb8620c in gdk_pixbuf_format_copy () from /usr/bin/cyggdk_pixbuf-2.0-0.dll
> > 
> > #30 0x6cb871cb in gdk_pixbuf_new_from_stream_at_scale () from /usr/bin/cyggdk_pixbuf-2.0-0.dll
> > 
> > #31 0x6bbae43d in gtk_icon_info_free () from /usr/bin/cyggtk-x11-2.0-0.dll
> > 
> > #32 0x6bbb169c in gtk_icon_info_load_icon () from /usr/bin/cyggtk-x11-2.0-0.dll
> > 
> > #33 0x00401eee in ?? ()
> > 
> > #34 0x004023ce in ?? ()
> > 
> > #35 0x0040249f in ?? ()
> > 
> > #36 0x004025fb in ?? ()
> > 
> > #37 0x00403bf3 in ?? ()
> > 
> > #38 0x61007a27 in cygwin_exit_return () from /usr/bin/cygwin1.dll
> > 
> > #39 0x00000001 in ?? ()
> > 
> > #40 0x0068cc6c in ?? ()
> > 
> > #41 0x610056c2 in _cygtls::call2(unsigned long (*)(void*, void*), void*, void*) () from /usr/bin/cygwin1.dll
> > (gdb)
> > 
> > It seems a problem with fontconfig. Any hint?
> 
> Could it be the same problem as this?
> 
> https://cygwin.com/ml/cygwin/2018-04/msg00325.html
> 
> Ken

Thanks for the reference, it seems the same problem. I have tried stracing the problem, but I don't see a clear failure in the trace log. The size is quite large, it's ~ 245 kB when bzipped, if someone is interested I can post it somewhere later.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: segfault in xwin-xdg-menu.exe
  2018-05-11 20:28   ` Fabio Rossi
@ 2018-05-12 14:43     ` Jon Turney
  2018-05-14 12:35       ` Fabio Rossi
  0 siblings, 1 reply; 9+ messages in thread
From: Jon Turney @ 2018-05-12 14:43 UTC (permalink / raw)
  To: The Cygwin Mailing List; +Cc: Fabio Rossi

On 11/05/2018 18:24, Fabio Rossi wrote:
>> Il 11 maggio 2018 alle 19.12 Ken Brown <kbrown@cornell.edu> ha scritto:
>>
>> On 5/11/2018 11:29 AM, Fabio Rossi wrote:
>>
>>> I have just made a fresh cygwin installation on windows 10 pro 32bit using setup 2.891. I have selected xorg-server, xinit, vim and gdb packages. I have modified the Xwin server configuration as described in https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-startxwinrc-exit and later I have successfully started it by using the action "cygwin-x\xwin server" under Windows programs menu. The X server is running with display :0.0 and its icon is visible in the tray bar.
>>>
>>> On another system installed months ago I have the xdg menu application already running (it's automatically started by the xwin startup script) but I didn't need to follow the above mentioned trick described in the FAQ.
>>>
>>> In a cygwin terminal I then try starting manually xwin-xdg-menu by using:
>>>
>>> $ DISPLAY=:0 xwin-xdg-menu.exe
>>>
>>> but I get a segmentation fault. With gdb I get the following backtrace:
>>>
[...]
>>>
>>> It seems a problem with fontconfig. Any hint?
>>
>> Could it be the same problem as this?
>>
>> https://cygwin.com/ml/cygwin/2018-04/msg00325.html
>>
> 
> Thanks for the reference, it seems the same problem. I have tried stracing the problem, but I don't see a clear failure in the trace log. The size is quite large, it's ~ 245 kB when bzipped, if someone is interested I can post it somewhere later.
> 

Yeah, this is the same problem, which is under investigation.

See also https://cygwin.com/ml/cygwin/2018-05/msg00152.html for another 
workaround.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: segfault in xwin-xdg-menu.exe
  2018-05-12 14:43     ` Jon Turney
@ 2018-05-14 12:35       ` Fabio Rossi
  2018-05-14 21:50         ` Jon Turney
  0 siblings, 1 reply; 9+ messages in thread
From: Fabio Rossi @ 2018-05-14 12:35 UTC (permalink / raw)
  To: The Cygwin Mailing List, Jon Turney

> Il 12 maggio 2018 alle 16.27 Jon Turney <jon.turney@dronecode.org.uk> ha scritto:
> 
> Yeah, this is the same problem, which is under investigation.
> 
> See also https://cygwin.com/ml/cygwin/2018-05/msg00152.html for another 
> workaround.

I have recompiled fontconfig and solved the issue as suggested in the other topic. Is it possible to update the binary packages installed by setup.exe?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: segfault in xwin-xdg-menu.exe
  2018-05-14 12:35       ` Fabio Rossi
@ 2018-05-14 21:50         ` Jon Turney
  0 siblings, 0 replies; 9+ messages in thread
From: Jon Turney @ 2018-05-14 21:50 UTC (permalink / raw)
  To: The Cygwin Mailing List; +Cc: Fabio Rossi

On 14/05/2018 08:50, Fabio Rossi wrote:
>> Il 12 maggio 2018 alle 16.27 Jon Turney ha scritto:
>>
>> Yeah, this is the same problem, which is under investigation.
>>
>> See also https://cygwin.com/ml/cygwin/2018-05/msg00152.html for another
>> workaround.
> 
> I have recompiled fontconfig and solved the issue as suggested in the
> other topic. Is it possible to update the binary packages installed
> by setup.exe?

This has been done.

https://cygwin.com/ml/cygwin/2018-05/msg00184.html

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2018-05-14 21:47 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-11 15:38 segfault in xwin-xdg-menu.exe Fabio Rossi
2018-05-11 15:54 ` Marco Atzeri
2018-05-11 16:26   ` Fabio Rossi
2018-05-11 16:46     ` Marco Atzeri
2018-05-11 17:25 ` Ken Brown
2018-05-11 20:28   ` Fabio Rossi
2018-05-12 14:43     ` Jon Turney
2018-05-14 12:35       ` Fabio Rossi
2018-05-14 21:50         ` Jon Turney

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).