Re: Segmentation fault on XpmCreateImageFromData(3)
On Thu, Mar 25, 2021 at 06:28:40PM +0100, Matthieu Herrb wrote: > On Wed, Mar 24, 2021 at 08:12:34PM -0300, Phillip Bushee wrote: > > I'm am writing a window manager which uses XpmCreateImageFromData(3) > > to read a .xpm file containing the theme of the decoration of the > > windows. The program segfaults when calling this function. I use this > > function rather than XpmCreatePixmapFromData(3) in order for me to get > > a pixel color from the .xpm with XGetPixel(3). > > Hi, > > I've the impression that this is happening because xa->valuemask is > being used unitialized in libXpm in the way you're calling it. PS : I forgot to mention that this is mentionned in xpm.PS.gz page 14: NOTE: In any case the XpmAttributes valuemask must be set to some valid value, at least zero, otherwise unpredictable errors can occur. > > This seems to fix the crash for me: > > diff --git shod.c shod.c > index 5dcb450..26865d7 100644 > --- shod.c > +++ shod.c > @@ -467,6 +467,7 @@ settheme(void) > unsigned int i, j; > int status; > > + memset(&xa, 0, sizeof(xa)); > if (config.theme_path) /* if the we have specified a file, read it > instead */ > status = XpmReadFileToImage(dpy, config.theme_path, &img, NULL, > &xa); > else/* else use the default theme */ > > > > > This is the code of the window manager: > > https://github.com/phillbush/shod/blob/master/shod.c > > > > This is the .xpm I am reading: > > https://github.com/phillbush/shod/blob/master/theme.xpm > > > > This is what I get running the program under gdb. > > > > GNU gdb 6.3 > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you > > are > > welcome to change it and/or distribute copies of it under certain > > conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for > > details. > > This GDB was configured as "amd64-unknown-openbsd6.8"... > > (gdb) run > > Starting program: /home/phil/proj/shod/shod > > Error while reading shared library symbols: > > Dwarf Error: wrong version in compilation unit header (is 4, should be > > 2) > > [in module /usr/libexec/ld.so] > > Error while reading shared library symbols: > > Dwarf Error: wrong version in compilation unit header (is 4, should be > > 2) > > [in module /usr/libexec/ld.so] > > Error while reading shared library symbols: > > Dwarf Error: wrong version in compilation unit header (is 4, should be > > 2) > > [in module /usr/libexec/ld.so] > > Error while reading shared library symbols: > > Dwarf Error: wrong version in compilation unit header (is 4, should be > > 2) > > [in module /usr/libexec/ld.so] > > Error while reading shared library symbols: > > Dwarf Error: wrong version in compilation unit header (is 4, should be > > 2) > > [in module /usr/libexec/ld.so] > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x7f7f2600 in ?? () > > (gdb) bt > > #0 0x7f7f2600 in ?? () > > #1 0x0960a406b734 in SetColor () from /usr/X11R6/lib/libXpm.so.9.0 > > #2 0x0960a4067ce6 in CreateColors () from > > /usr/X11R6/lib/libXpm.so.9.0 > > #3 0x0960a4069916 in xpmParseDataAndCreate () from > > /usr/X11R6/lib/libXpm.so.9.0 > > #4 0x0960a4065437 in XpmCreateImageFromData () from > > /usr/X11R6/lib/libXpm.so.9.0 > > #5 0x095e5e85f5db in settheme () at shod.c:473 > > #6 0x095e5e85bb58 in main () at shod.c:3465 > > > > I'm running OpenBSD Xenocara. > > This is what I get running `X -version`: > > > > X.Org X Server 1.20.8 > > X Protocol Version 11, Revision 0 > > Build Operating System: OpenBSD 6.8 amd64 > > Current Operating System: OpenBSD thinkbsd.my.domain 6.8 GENERIC.MP#5 > > amd64 > > Build Date: 24 November 2020 06:57:35AM > > > > Current version of pixman: 0.38.4 > > Before reporting problems, check http://wiki.x.org > > to make sure that you have the latest version. > > > > ___ > > xorg@lists.x.org: X.Org support > > Archives: http://lists.freedesktop.org/archives/xorg > > Info: https://lists.x.org/mailman/listinfo/xorg > > Your subscription address: %(user_address)s > > -- > Matthieu Herrb -- Matthieu Herrb ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Segmentation fault on XpmCreateImageFromData(3)
On Wed, Mar 24, 2021 at 08:12:34PM -0300, Phillip Bushee wrote: > I'm am writing a window manager which uses XpmCreateImageFromData(3) > to read a .xpm file containing the theme of the decoration of the > windows. The program segfaults when calling this function. I use this > function rather than XpmCreatePixmapFromData(3) in order for me to get > a pixel color from the .xpm with XGetPixel(3). Hi, I've the impression that this is happening because xa->valuemask is being used unitialized in libXpm in the way you're calling it. This seems to fix the crash for me: diff --git shod.c shod.c index 5dcb450..26865d7 100644 --- shod.c +++ shod.c @@ -467,6 +467,7 @@ settheme(void) unsigned int i, j; int status; + memset(&xa, 0, sizeof(xa)); if (config.theme_path) /* if the we have specified a file, read it instead */ status = XpmReadFileToImage(dpy, config.theme_path, &img, NULL, &xa); else/* else use the default theme */ > > This is the code of the window manager: > https://github.com/phillbush/shod/blob/master/shod.c > > This is the .xpm I am reading: > https://github.com/phillbush/shod/blob/master/theme.xpm > > This is what I get running the program under gdb. > > GNU gdb 6.3 > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "amd64-unknown-openbsd6.8"... > (gdb) run > Starting program: /home/phil/proj/shod/shod > Error while reading shared library symbols: > Dwarf Error: wrong version in compilation unit header (is 4, should be > 2) > [in module /usr/libexec/ld.so] > Error while reading shared library symbols: > Dwarf Error: wrong version in compilation unit header (is 4, should be > 2) > [in module /usr/libexec/ld.so] > Error while reading shared library symbols: > Dwarf Error: wrong version in compilation unit header (is 4, should be > 2) > [in module /usr/libexec/ld.so] > Error while reading shared library symbols: > Dwarf Error: wrong version in compilation unit header (is 4, should be > 2) > [in module /usr/libexec/ld.so] > Error while reading shared library symbols: > Dwarf Error: wrong version in compilation unit header (is 4, should be > 2) > [in module /usr/libexec/ld.so] > > Program received signal SIGSEGV, Segmentation fault. > 0x7f7f2600 in ?? () > (gdb) bt > #0 0x7f7f2600 in ?? () > #1 0x0960a406b734 in SetColor () from /usr/X11R6/lib/libXpm.so.9.0 > #2 0x0960a4067ce6 in CreateColors () from > /usr/X11R6/lib/libXpm.so.9.0 > #3 0x0960a4069916 in xpmParseDataAndCreate () from > /usr/X11R6/lib/libXpm.so.9.0 > #4 0x0960a4065437 in XpmCreateImageFromData () from > /usr/X11R6/lib/libXpm.so.9.0 > #5 0x095e5e85f5db in settheme () at shod.c:473 > #6 0x095e5e85bb58 in main () at shod.c:3465 > > I'm running OpenBSD Xenocara. > This is what I get running `X -version`: > > X.Org X Server 1.20.8 > X Protocol Version 11, Revision 0 > Build Operating System: OpenBSD 6.8 amd64 > Current Operating System: OpenBSD thinkbsd.my.domain 6.8 GENERIC.MP#5 > amd64 > Build Date: 24 November 2020 06:57:35AM > > Current version of pixman: 0.38.4 > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > > ___ > xorg@lists.x.org: X.Org support > Archives: http://lists.freedesktop.org/archives/xorg > Info: https://lists.x.org/mailman/listinfo/xorg > Your subscription address: %(user_address)s -- Matthieu Herrb ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Segmentation fault on XpmCreateImageFromData(3)
I'm am writing a window manager which uses XpmCreateImageFromData(3)
to read a .xpm file containing the theme of the decoration of the
windows. The program segfaults when calling this function. I use this
function rather than XpmCreatePixmapFromData(3) in order for me to get
a pixel color from the .xpm with XGetPixel(3).
This is the code of the window manager:
https://github.com/phillbush/shod/blob/master/shod.c
This is the .xpm I am reading:
https://github.com/phillbush/shod/blob/master/theme.xpm
This is what I get running the program under gdb.
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "amd64-unknown-openbsd6.8"...
(gdb) run
Starting program: /home/phil/proj/shod/shod
Error while reading shared library symbols:
Dwarf Error: wrong version in compilation unit header (is 4, should be
2) [in module /usr/libexec/ld.so]
Error while reading shared library symbols:
Dwarf Error: wrong version in compilation unit header (is 4, should be
2) [in module /usr/libexec/ld.so]
Error while reading shared library symbols:
Dwarf Error: wrong version in compilation unit header (is 4, should be
2) [in module /usr/libexec/ld.so]
Error while reading shared library symbols:
Dwarf Error: wrong version in compilation unit header (is 4, should be
2) [in module /usr/libexec/ld.so]
Error while reading shared library symbols:
Dwarf Error: wrong version in compilation unit header (is 4, should be
2) [in module /usr/libexec/ld.so]
Program received signal SIGSEGV, Segmentation fault.
0x7f7f2600 in ?? ()
(gdb) bt
#0 0x7f7f2600 in ?? ()
#1 0x0960a406b734 in SetColor () from /usr/X11R6/lib/libXpm.so.9.0
#2 0x0960a4067ce6 in CreateColors () from
/usr/X11R6/lib/libXpm.so.9.0
#3 0x0960a4069916 in xpmParseDataAndCreate () from
/usr/X11R6/lib/libXpm.so.9.0
#4 0x0960a4065437 in XpmCreateImageFromData () from
/usr/X11R6/lib/libXpm.so.9.0
#5 0x095e5e85f5db in settheme () at shod.c:473
#6 0x095e5e85bb58 in main () at shod.c:3465
I'm running OpenBSD Xenocara.
This is what I get running `X -version`:
X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
Build Operating System: OpenBSD 6.8 amd64
Current Operating System: OpenBSD thinkbsd.my.domain 6.8 GENERIC.MP#5
amd64
Build Date: 24 November 2020 06:57:35AM
Current version of pixman: 0.38.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
Re: segmentation fault
Hello: On 8 Jan 2018 at 11:55, François Patte wrote: > I try to install a multihead config with 2 video cards and 3 monitors, > using xinerama in order to have a unique screen. I'll see if I can help you with this. I am running PCLinuxOS: 4.12.10-pclos1 #1 SMP Wed Aug 30 08:17:56 CDT 2017 x86_64 x86_64 x86_64 GNU/Linux The desktop is MATE and I use two Nvidia video cards and three monitors,.but I do not use the Nouveau drivers. The driver I use is the is NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 and Xinerama. The installed cards are Quadro FX 370 and Quadro FX 580. Here's my xorg.conf for this setup. Some of the commented sections are for my control. --- # Revision 10 # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 340.104 (tex@localhost.localdomain) Tue Oct 3 03:43:15 CDT 2017 # File generated by XFdrake (rev 262502) # ** # Refer to the xorg.conf man page for details about the format of # this file. # ** # --- # # xorg.conf modified by CIV 20171016 for two Nvidia cards and three monitors # First slot: Quadro FX 370 - Second slot: Quadro FX 580 # See http://www.instructables.com/id/How-to-set-up-multiple-monitors-in-linux/ # See https://gist.github.com/mikaelj/5884579 # # Cards and bus addresses output from lspci # 01:00.0 VGA compatible controller: NVIDIA Corporation G84GL [Quadro FX 370] (rev a1) # 02:00.0 VGA compatible controller: NVIDIA Corporation G96GL [Quadro FX 580] (rev a1) # # Physical layout # _ __ __ # | || || | # | Screen 0 || Screen 1 || Screen 2 | # | 19" SM || 19" Dell|| 19" SM | # |___ __||__ ___||__ ___| # # --- Section "ServerLayout" Identifier"layout0" Screen 0"ScreenLeft" LeftOf "ScreenCenter" Screen 1"ScreenCenter" 0 0 Screen 2"ScreenRight" RightOf "ScreenCenter" Option"Xinerama" "1" EndSection Section "Extensions" #Option "Composite" "0" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "keyboard" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Samsung" ModelName "Samsung SyncMaster 940N" Option "DPMS" EndSection Section "Monitor" Identifier "Monitor1" VendorName "Dell" ModelName "Dell P1914S" Option "DPMS" EndSection Section "Monitor" Identifier "Monitor2" VendorName "Samsung" ModelName "Samsung SyncMaster 940N" Option "DPMS" EndSection Section "Device" Identifier "DeviceLeft" #card 1 Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "NVIDIA GeForce 8100 to GeForce 415" #NVIDIA G84GL Quadro FX 370 BusID "PCI:1:0:0" Screen 0 EndSection Section "Device" Identifier "DeviceCenter" #card 2 Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "NVIDIA GeForce 8100 to GeForce 415" #NVIDIA G96GL Quadro FX 580 BusID "PCI:2:0:0" EndSection Section "Device" Identifier "DeviceRight"#card 1 Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "NVIDIA GeForce 8100 to GeForce 415" #NVIDIA G84GL Quadro FX 370 BusID "PCI:1:0:0" Screen 1 EndSection Section "Screen" Identifier "ScreenLeft" Device "DeviceLeft" Monitor"Monitor0" DefaultDepth24 Option "DPMS" SubSection "Display" Depth 24 Modes "1280x1024" "1024x768" EndSubSection EndSection Section "Screen" Identifier "ScreenCenter" Device "DeviceCenter" Monitor"Monitor1" DefaultDepth24 Option "DPMS" SubSection "Display" Depth 24 Modes "1280x1024" "1024x768" EndSubSection EndSection Section "Screen" Identifier "ScreenRight" Device "DeviceRight" Monitor"Monitor2" DefaultDepth24 Option "DPMS" SubSection "Display" Depth 24 Modes "1280x1024" "1024x768" EndSubSection EndSection Section "Module" Load "v4l" # Video for Linux EndSection Section "ServerFlags" Option "allowmouseopenfail" "False" # default False allows server to start even if without mouse Option "DontZap" "False" # default False disables (server abort) Option "DontZoom" "False"# default False disables / (resolution switching) Option "AllowEmptyInput" "False" # default True if AAD an
segmentation fault
Bonjour, I try to install a multihead config with 2 video cards and 3 monitors, using xinerama in order to have a unique screen. But this does not work and end with a segmentation fault Here are the xorg.conf file and the corresponding log file. Thank you for helping. Here is my xorg.conf: <-xorg.conf- # essai xinerama Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 Screen 1 "Screen1" RightOf "Screen0" Screen 2 "Screen2" RightOf "Screen1" InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" Option "Xinerama" "1" EndSection Section "Files" FontPath"/usr/share/fonts/default/Type1" EndSection Section "Module" Load "dbe" Load "extmod" Load "type1" Load "freetype" Load "glx" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "keyboard" EndSection Section "Monitor" # HorizSync source: edid, VertRefresh source: edid Identifier "Monitor0" VendorName "LG" ModelName "LG Electronics L1952TQ" HorizSync 30.0 - 71.0 VertRefresh 56.0 - 75.0 Option "DPMS" EndSection Section "Monitor" # HorizSync source: edid, VertRefresh source: edid Identifier "Monitor1" VendorName "LG" ModelName "LG Electronics L1952TQ" HorizSync 30.0 - 71.0 VertRefresh 56.0 - 75.0 Option "DPMS" EndSection Section "Monitor" # HorizSync source: edid, VertRefresh source: edid Identifier "Monitor2" VendorName "LG" ModelName "LG Electronics L1920P" HorizSync 30.0 - 71.0 VertRefresh 56.0 - 75.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nouveau" BusId "PCI:1:0:0" VendorName "NVIDIA Corporation" BoardName "GeForce 8800 GT" Screen 0 EndSection Section "Device" Identifier "Device1" Driver "nouveau" BusId "PCI:1:0:0" VendorName "NVIDIA Corporation" BoardName "GeForce 8800 GT" Screen 1 EndSection Section "Device" Identifier "intel0" Driver "intel" BusId "PCI:0:2:0" VendorName "Intel Corporation" BoardName "Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller" Screen 0 #Option "AccelMethod" "uxa" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 #Option "Stereo" "0" #Option "nvidiaXineramaInfoOrder" "DFP-0" #Option "metamodes" "DVI-I-2: nvidia-auto-select +0+0, DVI-I-3: nvidia-auto-select +1280+0" #Option "SLI" "Off" #Option "MultiGPU" "Off" #Option "BaseMosaic" "off" SubSection "Display" Depth 24 EndSubSection EndSection Section "Screen" Identifier "Screen1" Device "Device1" Monitor"Monitor1" DefaultDepth24 #Option "Stereo" "0" #Option "nvidiaXineramaInfoOrder" "DFP-0" #Option "metamodes" "DVI-I-2: nvidia-auto-select +0+0, DVI-I-3: nvidia-auto-select +1280+0" #Option "SLI" "Off" #Option "MultiGPU" "Off" #Option "BaseMosaic" "off" SubSection "Display" Depth 24 EndSubSection EndSection Section "S
Re: Segmentation fault at adress 0x0 | nvidia Quadro K620M
To me it looks like something with Intel DDX driver. To check if it's true try creating a file /etc/X11/xorg.conf.d/20-modesetting.conf with content like: Section "Device" Identifier "Intel Graphics" Driver "modesetting" Option "Backlight" "intel_backlight" EndSection Then restart Xorg (alternatively reboot), it should stop crashing. On 23 October 2017 at 16:12, Christoph Hollizeck wrote: > Well hello there, I am kinda at the end of my wits as my Xserver broke again > after a restart (probably apt-get upgrade again) I tried all the stuff that > made it work last time again such as purging nvidia drivers, re-installing > gdm3 and gnome ( I usually don't use gnome, I use i3 but I have gnome as a > backup) I tried re-installing the xserver-xorg aswell but nothing really > worked googling the errors didn't help either and the log file told me to > ask the x.org support so here I am. Sadly I can't post my logfile cause > neither my git nor dropbox is working for some reason, and I can't mount my > /dev/sdb1 aswell otherwise I would have just reinstalled the whole system. > > Even tho I kinda know my way around linux I don't know what to do next I > would really appreciate some help > > Best regards Chris > -- > Sent from my phone. Please excuse my brevity. > > ___ > xorg@lists.x.org: X.Org support > Archives: http://lists.freedesktop.org/archives/xorg > Info: https://lists.x.org/mailman/listinfo/xorg > Your subscription address: %(user_address)s ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: xcb_writev: Segmentation fault
OK, I found how to fix the problem: I need to use the '-O1' gcc optimization flag instead of '-O2' when building libxcb. Well, in fact, it is just a workaround and not a fix because I prefer the '-O2' optimization flag but unfortunately I can't use it for building libxcb. Thanks to Ilya Lipnitskiy (lipnitsk) for this idea: https://bugs.archlinux.org/task/49560 On Thu, 31 Aug 2017 16:54:44 +0200 YuGiOhJCJ Mailing-List wrote: > Hello, > > I built libX11 1.6.5 32-bit on my 64-bit machine and I try to run a 32-bit > application: > --- > $ gdb 25Assist > GNU gdb (GDB) 7.11.1 > Copyright (C) 2016 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 "x86_64-slackware-linux". > 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 25Assist...(no debugging symbols found)...done. > (gdb) run > Starting program: /opt/25assist-20151223/25Assist > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > warning: File "/usr/lib/libstdc++.so.6.0.23-gdb.py" auto-loading has been > declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". > To enable execution of this file add > add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.23-gdb.py > line to your configuration file "/home/yugiohjcj/.gdbinit". > To completely disable this security protection add > set auto-load safe-path / > line to your configuration file "/home/yugiohjcj/.gdbinit". > For more information about this security protection see the > "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: > info "(gdb)Auto-loading safe path" > > Program received signal SIGSEGV, Segmentation fault. > 0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, > requests=73) at xcb_out.c:405 > 405 c->out.request += requests; > (gdb) bt > #0 0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, > requests=73) at xcb_out.c:405 > #1 0xf767f85e in _XSend (dpy=0x82cb400, data=0x0, size=0) at xcb_io.c:486 > #2 0xf767fe19 in _XReply (dpy=0x82cb400, rep=0x9ec4, extra=0, discard=1) > at xcb_io.c:573 > #3 0xf767b943 in XSync (dpy=0x82cb400, discard=0) at Sync.c:44 > #4 0xf7a537b2 in IA__gdk_flush () at gdkevents-x11.c:2606 > #5 0xf7a23170 in alloc_scratch_image (image_info=) at > gdkimage.c:527 > #6 _gdk_image_get_scratch (screen=0x82da0b8, width=160, height=23, depth=24, > x=0x9fbc, y=0x9fc0) at gdkimage.c:592 > #7 0xf7a30fbe in gdk_draw_rgb_image_core (image_info=0x83f3bf8, > drawable=drawable@entry=0x82c6c00, gc=gc@entry=0x82d8e80, x=0, y=0, > width=160, height=23, > buf=0x840bc48 "\371\371\371nnn\022\022\022", pixstride=3, rowstride=480, > conv=0xf7a2f0a0 , cmap=0x0, xdith=0, ydith=0) at > gdkrgb.c:3327 > #8 0xf7a329e9 in IA__gdk_draw_rgb_image (drawable=0x82c6c00, gc=0x82d8e80, > x=0, y=0, width=160, height=23, dith=GDK_RGB_DITHER_MAX, rgb_buf=0x840bc48 > "\371\371\371nnn\022\022\022", > rowstride=480) at gdkrgb.c:3393 > #9 0x0809d97e in ?? () > #10 0x081124a0 in ?? () > #11 0x081124d5 in ?? () > #12 0xf6252292 in ?? () > #13 0xf60cf138 in ?? () > #14 0xf60cf3a3 in ?? () > #15 0xf62d3f00 in ?? () > #16 0xf62ceb8b in ?? () > #17 0x0807077d in ?? () > #18 0x08070888 in ?? () > #19 0x08179267 in ?? () > #20 0xf6100128 in ?? () > #21 0x0816d65a in ?? () > #22 0x0816d64e in ?? () > #23 0x0816d75f in ?? () > #24 0xf668681b in ?? () > #25 0xf60b5308 in ?? () > #26 0xf60b53b4 in ?? () > #27 0xf6255333 in ?? () > #28 0xf60b5469 in ?? () > #29 0xf60b5024 in ?? () > #30 0x080d2592 in ?? () > #31 0x0816c1b1 in ?? () > #32 0xf72be4d3 in __libc_start_main () from /lib/libc.so.6 > #33 0x08052b21 in ?? () > (gdb) quit > A debugging session is active. > > Inferior 1 [process 18645] will be killed. > > Quit anyway? (y or n) y > --- > > As you can see I get a segmentation fault after the call to the xcb_writev
xcb_writev: Segmentation fault
Hello, I built libX11 1.6.5 32-bit on my 64-bit machine and I try to run a 32-bit application: --- $ gdb 25Assist GNU gdb (GDB) 7.11.1 Copyright (C) 2016 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 "x86_64-slackware-linux". 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 25Assist...(no debugging symbols found)...done. (gdb) run Starting program: /opt/25assist-20151223/25Assist [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". warning: File "/usr/lib/libstdc++.so.6.0.23-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.23-gdb.py line to your configuration file "/home/yugiohjcj/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/home/yugiohjcj/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" Program received signal SIGSEGV, Segmentation fault. 0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, requests=73) at xcb_out.c:405 405 c->out.request += requests; (gdb) bt #0 0xf6f1d6e1 in xcb_writev (c=0x82cbd50, vector=0x9e0c, count=3, requests=73) at xcb_out.c:405 #1 0xf767f85e in _XSend (dpy=0x82cb400, data=0x0, size=0) at xcb_io.c:486 #2 0xf767fe19 in _XReply (dpy=0x82cb400, rep=0x9ec4, extra=0, discard=1) at xcb_io.c:573 #3 0xf767b943 in XSync (dpy=0x82cb400, discard=0) at Sync.c:44 #4 0xf7a537b2 in IA__gdk_flush () at gdkevents-x11.c:2606 #5 0xf7a23170 in alloc_scratch_image (image_info=) at gdkimage.c:527 #6 _gdk_image_get_scratch (screen=0x82da0b8, width=160, height=23, depth=24, x=0x9fbc, y=0x9fc0) at gdkimage.c:592 #7 0xf7a30fbe in gdk_draw_rgb_image_core (image_info=0x83f3bf8, drawable=drawable@entry=0x82c6c00, gc=gc@entry=0x82d8e80, x=0, y=0, width=160, height=23, buf=0x840bc48 "\371\371\371nnn\022\022\022", pixstride=3, rowstride=480, conv=0xf7a2f0a0 , cmap=0x0, xdith=0, ydith=0) at gdkrgb.c:3327 #8 0xf7a329e9 in IA__gdk_draw_rgb_image (drawable=0x82c6c00, gc=0x82d8e80, x=0, y=0, width=160, height=23, dith=GDK_RGB_DITHER_MAX, rgb_buf=0x840bc48 "\371\371\371nnn\022\022\022", rowstride=480) at gdkrgb.c:3393 #9 0x0809d97e in ?? () #10 0x081124a0 in ?? () #11 0x081124d5 in ?? () #12 0xf6252292 in ?? () #13 0xf60cf138 in ?? () #14 0xf60cf3a3 in ?? () #15 0xf62d3f00 in ?? () #16 0xf62ceb8b in ?? () #17 0x0807077d in ?? () #18 0x08070888 in ?? () #19 0x08179267 in ?? () #20 0xf6100128 in ?? () #21 0x0816d65a in ?? () #22 0x0816d64e in ?? () #23 0x0816d75f in ?? () #24 0xf668681b in ?? () #25 0xf60b5308 in ?? () #26 0xf60b53b4 in ?? () #27 0xf6255333 in ?? () #28 0xf60b5469 in ?? () #29 0xf60b5024 in ?? () #30 0x080d2592 in ?? () #31 0x0816c1b1 in ?? () #32 0xf72be4d3 in __libc_start_main () from /lib/libc.so.6 #33 0x08052b21 in ?? () (gdb) quit A debugging session is active. Inferior 1 [process 18645] will be killed. Quit anyway? (y or n) y --- As you can see I get a segmentation fault after the call to the xcb_writev function. From this program stack, I am unable to guess what could be the problem. Maybe a communication problem between libX11 and libxcb but why? I was able to run this application in the past so I think I did something wrong when I built my 32-bit libX11 this time. Can you guess where the problem is from this backtrace? Thank you. Best regards. Remark: I rebuilt gtk+2, libX11 and libxcb with the '-g' flag to have a nice backtrace so that's why you see the debugging symbols. 32-bit programs used: atk-2.20.0 cairo-1.14.10 expat-2.1.0 fontconfig-2.12.1 freetype-2.6.3 gdk-pixbuf2-2.36.6 glib2-2.52.3 glibc-2.23 gtk+2-2.24.30 harfbuzz-1.2.7 icu4c-56.1 libdrm-2.4.80 libffi-3.2.1 libjpeg-turbo-1.5.0 libpciaccess-0.13.5 libpng-1.6.25 libtiff-4.0.6 libX11-1.6.5 libXau-1.0.8 libxcb-1.12 libXcomposite-0.4.4 libXcursor-1.1.14 libXdamage-1.1.4 libXext-1.3.3 libXfixes-5.0.3 libXft-2.3
Re: Caught signal 11 (Segmentation fault). Server aborting
I finally got this segmentation fault problem fixed. I uninstalled the following drivers: xf86-input-keyboard-1.7.0 xf86-input-mouse-1.9.0 xf86-input-synaptics-1.7.1 xf86-video-ati-7.2.0 xf86-video-modesetting-0.8.0 xf86-video-vesa-2.3.3 Only the two drivers below remained: xf86-input-evdev-2.8.2 xf86-video-fbdev-0.4.4 Now, startx works as expected. I think the segmentation fault I had came from the ati video driver. Because I use the kernel Linux-libre (http://www.fsfla.org/ikiwiki/selibre/linux-libre/) from which binary blobs and non-free files are removed, the binary firmware (firmware/radeon in the kernel Linux sources) used by the ati video driver to provide hardware acceleration was not present, hence the segmentation fault. Christophe ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Caught signal 11 (Segmentation fault). Server aborting
I finally got this segmentation fault problem fixed. I uninstalled the following drivers: xf86-input-keyboard-1.7.0 xf86-input-mouse-1.9.0 xf86-input-synaptics-1.7.1 xf86-video-ati-7.2.0 xf86-video-modesetting-0.8.0 xf86-video-vesa-2.3.3 Only the two drivers below remained: xf86-input-evdev-2.8.2 xf86-video-fbdev-0.4.4 Now, startx works as expected. I think the segmentation fault I had came from the ati video driver. Because I use the kernel Linux-libre (http://www.fsfla.org/ikiwiki/selibre/linux-libre/) from which binary blobs and non-free files are removed, the binary firmware (firmware/radeon in the kernel Linux sources) used by the ati video driver to provide hardware acceleration was not present, hence the segmentation fault. Christophe ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Caught signal 11 (Segmentation fault). Server aborting
I followed Version 1 of
http://www.x.org/wiki/Development/Documentation/ServerDebugging/#OneMachine and
the complete gdb_log.1034 is attached. The interesting part of this file seems
to be:
Program received signal SIGSEGV, Segmentation fault.
0x2b25060c in memset () from /lib/libc.so.6
#0 0x2b25060c in memset () from /lib/libc.so.6
No symbol table info available.
#1 0x2b4bafd0 in drmmode_copy_fb (pScrn=0x1024cbb0, drmmode=)
at drmmode_display.c:434 xf86_config =
info = 0x1024d0c8
src = 0x10228c58
dst =
pScreen = 0x10252760
fbcon_id =
i =
pitch =
tiling_flags = 0
ret =
#2 0x2b4bc214 in drmmode_set_desired_modes (pScrn=0x1024cbb0,
drmmode=0x1024d240) at drmmode_display.c:1823 config = 0x1024e9a0
c =
#3 0x2b4b559c in RADEONCreateScreenResources_KMS (pScreen=0x10252760) at
radeon_kms.c:223 pScrn = 0x1024cbb0
info = 0x1024d0c8
pixmap =
#4 0x100c7198 in xf86CrtcCreateScreenResources (screen=0x10252760) at
xf86Crtc.c:707 scrn =
config =
#5 0x10021f54 in main (argc=1, argv=0x7faa81c4, envp=) at
main.c:225 pScreen = 0x10252760
i =
alwaysCheckForInput = {0, 1}
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/Xorg (xorg_backtrace+0x68) [0x101d29a8]
(EE)
(EE) Segmentation fault at address 0x0
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional
information. (EE)
(EE) Server terminated with error (1). Closing log file.
Program received signal SIGABRT, Aborted.
0x2b1fa578 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:66
66 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
Does someone understand where the problem comes from?
Thans,
Christophe
gdb_log.1034
Description: Binary data
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Caught signal 11 (Segmentation fault). Server aborting
Dear list, I built Xorg and dependancies. When I try to launch X with startx, it does not start. The failure message in /var/log/Xorg.0.log is: Backtrace: 0: /usr/bin/X (xorg_backtrace+0x68) [0x10194fd8] Segmentation fault at address (nil) Fatal server error: Caught signal 11 (Segmentation fault). Server aborting The complete Xorg.0.log is attached. Do you know how to fix this issue? Thanks, Christophe Xorg.0.log Description: Binary data ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault
>On Tue, Dec 11, 2012 at 5:48 AM, stompdagg...@yahoo.com > wrote: >>>On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote: >>>> >On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote: >>>>> >> On Sun, Dec 9, 2012 at 12:16 PM, >>>> wrote: >>>> >> >> When starting openSuse 12.2, the X-server terminates with a >>>> >> segmentation fault (see attached log file). >>>> >> >>>> >> >The open source driver should support your card just fine. Can >>>> you >>>> >> >install debugging symbols and get a proper backtrace with GDB? >>>> >> >http://wiki.x.org/wiki/Development/Documentation/ServerDebugging >>>> >> >>>> >> Alex, looking at his log, I don't see the card in the support list, >>>> >> his card is the v7700? >>>> >>>> >As you can see in the lspci output, it's a 7500, which is Turks >>>> >(Northern Islands generation) based. >>>> >>>> >If the driver didn't support the card, it would bail much earlier. >>>> >>>> looking at the xorg log, I see Turks only as part of the AMD Radeon HD >>>> 6700 Series, does this means that 7500 Series is part of the 6700 >>>> Series? >> >>>It's complicated. :\ >> >>>7xx0 and 6xx0 are marketing names, which are mostly irrelevant for >>>driver support, in contrast to code names such as Turks, Northern >>>Islands etc. >> >> I see, so maybe it is a good idea to fix the radeon output? if I had this >> problem, I'd assume that the driver doesn't supports the card, this would >> have wasted a lot of time. >Marketing and OEMs come up with so many different names, it's hard to >keep track. Best bet it to look at the pci ids, or check wikipedia: >http://en.wikipedia.org/wiki/Ati_gpu >Alex I see, thanks for the explanation. ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault
>On Die, 2012-12-11 at 02:48 -0800, stompdagg...@yahoo.com wrote: >> >On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote: >> >> >On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote: > >>> >> On Sun, Dec 9, 2012 at 12:16 PM, > >>> wrote: >> >> >> >> When starting openSuse 12.2, the X-server terminates with a >> >> >> segmentation fault (see attached log file). > >>> >> > >>> >> >The open source driver should support your card just fine. Can >> >> you >> >> >> >install debugging symbols and get a proper backtrace with GDB? > >>> >> >> >http://wiki.x.org/wiki/Development/Documentation/ServerDebugging >> >> >> > >>> >> Alex, looking at his log, I don't see the card in the support >> list, >> >> >> his card is the v7700? > >>> > >>> >As you can see in the lspci output, it's a 7500, which is Turks >> >> >(Northern Islands generation) based. >> >> >> >> >If the driver didn't support the card, it would bail much >> earlier. >> >> > >>> looking at the xorg log, I see Turks only as part of the AMD Radeon >> HD >> >> 6700 Series, does this means that 7500 Series is part of the 6700 > >>> Series? >> >> >It's complicated. :\ >> >> >7xx0 and 6xx0 are marketing names, which are mostly irrelevant for >> >driver support, in contrast to code names such as Turks, Northern >> >Islands etc. >> >> I see, so maybe it is a good idea to fix the radeon output? >Can you make a specific suggestion, or even a patch? I can't seem to find something more specific than this scenario, >> if I had this problem, I'd assume that the driver doesn't supports the >> card, this would have wasted a lot of time. >Why would you assume that? I think it is extremely logical to assume that because xorg's log contains the following line: "(II) RADEON: Driver for ATI Radeon chipsets:" and is followed by a list of cards. if the card you have is not on the list, it is logical to assume that the driver doesn't supports it. > Again, if the driver doesn't support a card, >it bails much earlier, in a totally different way. for you it is logical because you know your way around the code, I consider myself as an advanced linux user, if for me it isn't clear, why would it be clear to someone at lower experience level than I?___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault
On Tue, Dec 11, 2012 at 5:48 AM, stompdagg...@yahoo.com wrote: >>On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote: >>> >On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote: >>> >> On Sun, Dec 9, 2012 at 12:16 PM, >>> wrote: >>> >> >> When starting openSuse 12.2, the X-server terminates with a >>> >> segmentation fault (see attached log file). >>> >> >>> >> >The open source driver should support your card just fine. Can >>> you >>> >> >install debugging symbols and get a proper backtrace with GDB? >>> >> >http://wiki.x.org/wiki/Development/Documentation/ServerDebugging >>> >> >>> >> Alex, looking at his log, I don't see the card in the support list, >>> >> his card is the v7700? >>> >>> >As you can see in the lspci output, it's a 7500, which is Turks >>> >(Northern Islands generation) based. >>> >>> >If the driver didn't support the card, it would bail much earlier. >>> >>> looking at the xorg log, I see Turks only as part of the AMD Radeon HD >>> 6700 Series, does this means that 7500 Series is part of the 6700 >>> Series? > >>It's complicated. :\ > >>7xx0 and 6xx0 are marketing names, which are mostly irrelevant for >>driver support, in contrast to code names such as Turks, Northern >>Islands etc. > > I see, so maybe it is a good idea to fix the radeon output? if I had this > problem, I'd assume that the driver doesn't supports the card, this would > have wasted a lot of time. Marketing and OEMs come up with so many different names, it's hard to keep track. Best bet it to look at the pci ids, or check wikipedia: http://en.wikipedia.org/wiki/Ati_gpu Alex ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault
On Die, 2012-12-11 at 02:48 -0800, stompdagg...@yahoo.com wrote: > >On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote: > >> >On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote: > >> >> On Sun, Dec 9, 2012 at 12:16 PM, > >> wrote: > >> >> >> When starting openSuse 12.2, the X-server terminates with a > >> >> segmentation fault (see attached log file). > >> >> > >> >> >The open source driver should support your card just fine. Can > >> you > >> >> >install debugging symbols and get a proper backtrace with GDB? > >> >> > >http://wiki.x.org/wiki/Development/Documentation/ServerDebugging > >> >> > >> >> Alex, looking at his log, I don't see the card in the support > list, > >> >> his card is the v7700? > >> > >> >As you can see in the lspci output, it's a 7500, which is Turks > >> >(Northern Islands generation) based. > >> > >> >If the driver didn't support the card, it would bail much > earlier. > >> > >> looking at the xorg log, I see Turks only as part of the AMD Radeon > HD > >> 6700 Series, does this means that 7500 Series is part of the 6700 > >> Series? > > >It's complicated. :\ > > >7xx0 and 6xx0 are marketing names, which are mostly irrelevant for > >driver support, in contrast to code names such as Turks, Northern > >Islands etc. > > I see, so maybe it is a good idea to fix the radeon output? Can you make a specific suggestion, or even a patch? > if I had this problem, I'd assume that the driver doesn't supports the > card, this would have wasted a lot of time. Why would you assume that? Again, if the driver doesn't support a card, it bails much earlier, in a totally different way. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault
>On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote: >> >On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote: >> >> On Sun, Dec 9, 2012 at 12:16 PM, >> wrote: >> >> >> When starting openSuse 12.2, the X-server terminates with a >> >> segmentation fault (see attached log file). >> >> >> >> >The open source driver should support your card just fine. Can >> you >> >> >install debugging symbols and get a proper backtrace with GDB? >> >> >http://wiki.x.org/wiki/Development/Documentation/ServerDebugging >> >> >> >> Alex, looking at his log, I don't see the card in the support list, >> >> his card is the v7700? >> >> >As you can see in the lspci output, it's a 7500, which is Turks >> >(Northern Islands generation) based. >> >> >If the driver didn't support the card, it would bail much earlier. >> >> looking at the xorg log, I see Turks only as part of the AMD Radeon HD >> 6700 Series, does this means that 7500 Series is part of the 6700 >> Series? >It's complicated. :\ >7xx0 and 6xx0 are marketing names, which are mostly irrelevant for >driver support, in contrast to code names such as Turks, Northern >Islands etc. I see, so maybe it is a good idea to fix the radeon output? if I had this problem, I'd assume that the driver doesn't supports the card, this would have wasted a lot of time. ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault
On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote: > >On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote: > >> On Sun, Dec 9, 2012 at 12:16 PM, > wrote: > >> >> When starting openSuse 12.2, the X-server terminates with a > >> segmentation fault (see attached log file). > >> > >> >The open source driver should support your card just fine. Can > you > >> >install debugging symbols and get a proper backtrace with GDB? > >> >http://wiki.x.org/wiki/Development/Documentation/ServerDebugging > >> > >> Alex, looking at his log, I don't see the card in the support list, > >> his card is the v7700? > > >As you can see in the lspci output, it's a 7500, which is Turks > >(Northern Islands generation) based. > > >If the driver didn't support the card, it would bail much earlier. > > looking at the xorg log, I see Turks only as part of the AMD Radeon HD > 6700 Series, does this means that 7500 Series is part of the 6700 > Series? It's complicated. :\ 7xx0 and 6xx0 are marketing names, which are mostly irrelevant for driver support, in contrast to code names such as Turks, Northern Islands etc. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault
>On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote: >> On Sun, Dec 9, 2012 at 12:16 PM, wrote: >> >> When starting openSuse 12.2, the X-server terminates with a >> segmentation fault (see attached log file). >> >> >The open source driver should support your card just fine. Can you >> >install debugging symbols and get a proper backtrace with GDB? >> >http://wiki.x.org/wiki/Development/Documentation/ServerDebugging >> >> Alex, looking at his log, I don't see the card in the support list, >> his card is the v7700? >As you can see in the lspci output, it's a 7500, which is Turks >(Northern Islands generation) based. >If the driver didn't support the card, it would bail much earlier. looking at the xorg log, I see Turks only as part of the AMD Radeon HD 6700 Series, does this means that 7500 Series is part of the 6700 Series?___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault
On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote: > On Sun, Dec 9, 2012 at 12:16 PM, wrote: > >> When starting openSuse 12.2, the X-server terminates with a > segmentation fault (see attached log file). > > >The open source driver should support your card just fine. Can you > >install debugging symbols and get a proper backtrace with GDB? > >http://wiki.x.org/wiki/Development/Documentation/ServerDebugging > > Alex, looking at his log, I don't see the card in the support list, > his card is the v7700? As you can see in the lspci output, it's a 7500, which is Turks (Northern Islands generation) based. If the driver didn't support the card, it would bail much earlier. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault
On Sun, Dec 9, 2012 at 12:16 PM, wrote: >> When starting openSuse 12.2, the X-server terminates with a segmentation >> fault (see attached log file). >The open source driver should support your card just fine. Can you >install debugging symbols and get a proper backtrace with GDB? >http://wiki.x.org/wiki/Development/Documentation/ServerDebugging Alex, looking at his log, I don't see the card in the support list, his card is the v7700?___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault
On Sun, Dec 9, 2012 at 12:16 PM, wrote: > When starting openSuse 12.2, the X-server terminates with a segmentation > fault (see attached log file). The open source driver should support your card just fine. Can you install debugging symbols and get a proper backtrace with GDB? http://wiki.x.org/wiki/Development/Documentation/ServerDebugging Alex ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault
it seems that you have two drivers on your system, as radeonhd is deprecated and doesn't supports your card, you'll need remove it. also the radeon version that you have seems to lack support for your card, afaik, your card isn't supported enough in newer versions on radeon so I'd recommend installing fgrlx. From: "olivier.e.am...@gmail.com" To: x...@freedesktop.org Sent: Sunday, December 9, 2012 7:16 PM Subject: Segmentation fault When starting openSuse 12.2, the X-server terminates with a segmentation fault (see attached log file). The lspci output for the graphics card is: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Turks [Radeon HD 7500 Series] [1002:675d] (prog-if 00 [VGA controller]) Subsystem: Device [1b0a:90bd] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at e000 (64-bit, prefetchable) [size=256M] Memory at f7e2 (64-bit, non-prefetchable) [size=128K] I/O ports at e000 [size=256] Expansion ROM at f7e0 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150] Advanced Error Reporting ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: stompdagg...@yahoo.com___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Segmentation fault
When starting openSuse 12.2, the X-server terminates with a segmentation fault (see attached log file). The lspci output for the graphics card is: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Turks [Radeon HD 7500 Series] [1002:675d] (prog-if 00 [VGA controller]) Subsystem: Device [1b0a:90bd] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at e000 (64-bit, prefetchable) [size=256M] Memory at f7e2 (64-bit, non-prefetchable) [size=128K] I/O ports at e000 [size=256] Expansion ROM at f7e0 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150] Advanced Error Reporting Xorg.0.log.old Description: application/trash ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault starting X with xorg-server version 1.12.3 and xf86-video-ati version 6.14.4
Am 25.07.2012 15:19, schrieb Alex Deucher: > On Wed, Jul 25, 2012 at 5:33 AM, Andreas Gick wrote: >> Hi, >> >> on my gentoo powered laptop X refuses to work. When I type startx, the X >> server terminates with a segmentation fault. >> >> This is the backtrace that I found in /var/log/Xorg.0.log >> >> [ 20298.142] 0: /usr/bin/X (xorg_backtrace+0x36) [0x56eeb6] >> [ 20298.142] 1: /usr/bin/X (0x40+0x172ec9) [0x572ec9] >> [ 20298.142] 2: /lib64/libpthread.so.0 (0x7f14caa72000+0x107f0) >> [0x7f14caa827f0] >> [ 20298.142] 3: /usr/lib64/xorg/modules/drivers/radeon_drv.so >> (0x7f14c7ac8000+0xc6e8e) [0x7f14c7b8ee8e] >> [ 20298.143] 4: /usr/lib64/xorg/modules/drivers/radeon_drv.so >> (0x7f14c7ac8000+0xc0839) [0x7f14c7b88839] >> [ 20298.143] 5: /usr/lib64/xorg/modules/libexa.so >> (0x7f14c7057000+0x9ade) [0x7f14c7060ade] >> [ 20298.143] 6: /usr/lib64/xorg/modules/libexa.so >> (0x7f14c7057000+0xa76d) [0x7f14c706176d] >> [ 20298.143] 7: /usr/bin/X (0x40+0xfab8f) [0x4fab8f] >> [ 20298.143] 8: /usr/bin/X (miPaintWindow+0x1ca) [0x54fbaa] >> [ 20298.143] 9: /usr/bin/X (miWindowExposures+0xb4) [0x5500d4] >> [ 20298.143] 10: /usr/lib64/xorg/modules/extensions/libdri.so >> (DRIWindowExposures+0x83) [0x7f14c8207043] >> [ 20298.143] 11: /usr/bin/X (0x40+0x8b6fb) [0x48b6fb] >> [ 20298.143] 12: /usr/bin/X (MapWindow+0x2e1) [0x461ae1] >> [ 20298.143] 13: /usr/bin/X (0x40+0x24e55) [0x424e55] >> [ 20298.143] 14: /lib64/libc.so.6 (__libc_start_main+0xec) [0x7f14c99ac28c] >> [ 20298.143] 15: /usr/bin/X (0x40+0x24a09) [0x424a09] >> [ 20298.143] >> [ 20298.143] Segmentation fault at address 0x9c >> >> These are the warnings and error messages in the same file: >> >> (WW) The directory "/usr/share/fonts/TTF/" does not exist. >> [ 20296.972] (WW) The directory "/usr/share/fonts/OTF/" does not exist. >> [ 20296.972] (WW) The directory "/usr/share/fonts/Type1/" does not exist. >> [ 20296.972] (WW) `fonts.dir' not found (or not valid) in >> "/usr/share/fonts/100dpi/". >> [ 20296.972] (WW) `fonts.dir' not found (or not valid) in >> "/usr/share/fonts/75dpi/". >> [ 20296.974] (II) Loading extension MIT-SCREEN-SAVER >> [ 20296.991] (WW) RADEON(0): LVDS Info: >> [ 20297.818] (WW) RADEON(0): DRI init changed memory map, adjusting ... >> [ 20297.818] (WW) RADEON(0): MC_FB_LOCATION was: 0x00cf00c0 is: >> 0x00cf00c0 >> [ 20297.818] (WW) RADEON(0): MC_AGP_LOCATION was: 0x003f is: >> 0x0003 >> [ 20298.121] (WW) RADEON(0): Option "VendorName" is not used >> [ 20298.121] (WW) RADEON(0): Option "ModelName" is not used >> [ 20298.132] (EE) AIGLX error: r600 does not export required DRI extension >> [ 20298.132] (EE) AIGLX: reverting to software rendering >> >> Finally lspci -v information about the graphics card: >> >> 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI >> RS880M [Mobility Radeon HD 4200 Series] ( >> prog-if 00 [VGA controller]) >> Subsystem: Hewlett-Packard Company Device 1475 >> Flags: bus master, fast devsel, latency 0, IRQ 18 >> Memory at 8000 (32-bit, prefetchable) [size=256M] >> I/O ports at 5000 [size=256] >> Memory at 9430 (32-bit, non-prefetchable) [size=64K] >> Memory at 9420 (32-bit, non-prefetchable) [size=1M] >> Expansion ROM at [disabled] >> Capabilities: [50] Power Management version 3 >> Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ >> >> The complete Xorg.0.log is attached to this mail. >> >> Is there anything else I should post to find a solution to this problem? > > Is there any reason you are using UMS rather than KMS? UMS is not > really supported any more. If you still want to use UMS, I would > suggest trying a newer release of the driver. > > Alex Hi Alex, thanks for your hint, it actually solved my problem. I didn't use kms, because I wanted to revert back to the proprietary ati-driver with which I had problems in the hope that the new version would still support my card. That's why I didn't care too much about the configuration of the radeon driver. But as of the latest version ati/amd cancelled the support for it. Regards Andreas ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: Segmentation fault starting X with xorg-server version 1.12.3 and xf86-video-ati version 6.14.4
On Wed, Jul 25, 2012 at 5:33 AM, Andreas Gick wrote: > Hi, > > on my gentoo powered laptop X refuses to work. When I type startx, the X > server terminates with a segmentation fault. > > This is the backtrace that I found in /var/log/Xorg.0.log > > [ 20298.142] 0: /usr/bin/X (xorg_backtrace+0x36) [0x56eeb6] > [ 20298.142] 1: /usr/bin/X (0x40+0x172ec9) [0x572ec9] > [ 20298.142] 2: /lib64/libpthread.so.0 (0x7f14caa72000+0x107f0) > [0x7f14caa827f0] > [ 20298.142] 3: /usr/lib64/xorg/modules/drivers/radeon_drv.so > (0x7f14c7ac8000+0xc6e8e) [0x7f14c7b8ee8e] > [ 20298.143] 4: /usr/lib64/xorg/modules/drivers/radeon_drv.so > (0x7f14c7ac8000+0xc0839) [0x7f14c7b88839] > [ 20298.143] 5: /usr/lib64/xorg/modules/libexa.so > (0x7f14c7057000+0x9ade) [0x7f14c7060ade] > [ 20298.143] 6: /usr/lib64/xorg/modules/libexa.so > (0x7f14c7057000+0xa76d) [0x7f14c706176d] > [ 20298.143] 7: /usr/bin/X (0x40+0xfab8f) [0x4fab8f] > [ 20298.143] 8: /usr/bin/X (miPaintWindow+0x1ca) [0x54fbaa] > [ 20298.143] 9: /usr/bin/X (miWindowExposures+0xb4) [0x5500d4] > [ 20298.143] 10: /usr/lib64/xorg/modules/extensions/libdri.so > (DRIWindowExposures+0x83) [0x7f14c8207043] > [ 20298.143] 11: /usr/bin/X (0x40+0x8b6fb) [0x48b6fb] > [ 20298.143] 12: /usr/bin/X (MapWindow+0x2e1) [0x461ae1] > [ 20298.143] 13: /usr/bin/X (0x40+0x24e55) [0x424e55] > [ 20298.143] 14: /lib64/libc.so.6 (__libc_start_main+0xec) [0x7f14c99ac28c] > [ 20298.143] 15: /usr/bin/X (0x40+0x24a09) [0x424a09] > [ 20298.143] > [ 20298.143] Segmentation fault at address 0x9c > > These are the warnings and error messages in the same file: > > (WW) The directory "/usr/share/fonts/TTF/" does not exist. > [ 20296.972] (WW) The directory "/usr/share/fonts/OTF/" does not exist. > [ 20296.972] (WW) The directory "/usr/share/fonts/Type1/" does not exist. > [ 20296.972] (WW) `fonts.dir' not found (or not valid) in > "/usr/share/fonts/100dpi/". > [ 20296.972] (WW) `fonts.dir' not found (or not valid) in > "/usr/share/fonts/75dpi/". > [ 20296.974] (II) Loading extension MIT-SCREEN-SAVER > [ 20296.991] (WW) RADEON(0): LVDS Info: > [ 20297.818] (WW) RADEON(0): DRI init changed memory map, adjusting ... > [ 20297.818] (WW) RADEON(0): MC_FB_LOCATION was: 0x00cf00c0 is: > 0x00cf00c0 > [ 20297.818] (WW) RADEON(0): MC_AGP_LOCATION was: 0x003f is: > 0x0003 > [ 20298.121] (WW) RADEON(0): Option "VendorName" is not used > [ 20298.121] (WW) RADEON(0): Option "ModelName" is not used > [ 20298.132] (EE) AIGLX error: r600 does not export required DRI extension > [ 20298.132] (EE) AIGLX: reverting to software rendering > > Finally lspci -v information about the graphics card: > > 01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI > RS880M [Mobility Radeon HD 4200 Series] ( > prog-if 00 [VGA controller]) > Subsystem: Hewlett-Packard Company Device 1475 > Flags: bus master, fast devsel, latency 0, IRQ 18 > Memory at 8000 (32-bit, prefetchable) [size=256M] > I/O ports at 5000 [size=256] > Memory at 9430 (32-bit, non-prefetchable) [size=64K] > Memory at 9420 (32-bit, non-prefetchable) [size=1M] > Expansion ROM at [disabled] > Capabilities: [50] Power Management version 3 > Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ > > The complete Xorg.0.log is attached to this mail. > > Is there anything else I should post to find a solution to this problem? Is there any reason you are using UMS rather than KMS? UMS is not really supported any more. If you still want to use UMS, I would suggest trying a newer release of the driver. Alex ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: X Segmentation fault with i810
On Wed, Jan 4, 2012 at 11:03 PM, Jeff Chua wrote:
> On Wed, Jan 4, 2012 at 2:17 AM, Adam Jackson wrote:
>> On 1/3/12 1:00 PM, Adam Jackson wrote:
>>> On 1/3/12 12:49 PM, Chris Wilson wrote:
On Tue, 03 Jan 2012 12:02:43 -0500, Adam Jackson wrote:
> On 12/30/11 12:34 AM, Jeff Chua wrote:
>> Something like this?
>>
>> ---
>> diff --git a/hw/xfree86/vgahw/vgaHW.h b/hw/xfree86/vgahw/vgaHW.h
>> index e943aa3..9fa8183 100644
>> --- a/hw/xfree86/vgahw/vgaHW.h
>> +++ b/hw/xfree86/vgahw/vgaHW.h
>> @@ -170,10 +170,10 @@ typedef struct _vgaHWRec {
>> #define BITS_PER_GUN 6
>> #define COLORMAP_SIZE 256
>>
>> -#define DACDelay(hw) \
>> - do { \
>> - pci_io_read8((hw)->io, (hw)->IOBase + VGA_IN_STAT_1_OFFSET); \
>> - pci_io_read8((hw)->io, (hw)->IOBase + VGA_IN_STAT_1_OFFSET); \
>> +#define DACDelay(hw) \
>> + do { \
>> + (hw)->readST01((hw)); \
>> + (hw)->readST01((hw)); \
>> } while (0)
>>
>> /* Function Prototypes */
Yes! That works!
Thank you, everything on latest xorg again! Happy!
Jeff
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: X Segmentation fault with i810
On Wed, Jan 4, 2012 at 2:17 AM, Adam Jackson wrote:
> On 1/3/12 1:00 PM, Adam Jackson wrote:
>>
>> On 1/3/12 12:49 PM, Chris Wilson wrote:
>>>
>>> On Tue, 03 Jan 2012 12:02:43 -0500, Adam Jackson wrote:
On 12/30/11 12:34 AM, Jeff Chua wrote:
> How can I go about to help debug this?
The i810 driver probably needs the equivalent fix as:
http://cgit.freedesktop.org/xorg/driver/xf86-video-cirrus/commit/?id=f422d0c38b0befdb2152215ab05d0d14f3da3ed9
>>>
>>> The i810 driver uses vgaHWSetMmioFuncs() rather than SetStdFuncs, and so
>>> leaves hwp->io uninitialised. That pointer is then dereferenced by
>>> DACDelay() (as it uses pci_io_read8 irrespective of mmio/std funcs)
>>> during
>>> the vgaHWSaveColormap(). At which point, I'm far beyond my comfort
>>> zone...
>>> -Chris
>>>
>>
>> Oof, okay, nice find. DACDelay needs to not do that, or at least, not
>> unconditionally. I'll look into it.
>
>
> Something like this?
>
> ---
> diff --git a/hw/xfree86/vgahw/vgaHW.h b/hw/xfree86/vgahw/vgaHW.h
> index e943aa3..9fa8183 100644
> --- a/hw/xfree86/vgahw/vgaHW.h
> +++ b/hw/xfree86/vgahw/vgaHW.h
> @@ -170,10 +170,10 @@ typedef struct _vgaHWRec {
> #define BITS_PER_GUN 6
> #define COLORMAP_SIZE 256
>
> -#define DACDelay(hw) \
> - do { \
> - pci_io_read8((hw)->io, (hw)->IOBase + VGA_IN_STAT_1_OFFSET); \
> - pci_io_read8((hw)->io, (hw)->IOBase + VGA_IN_STAT_1_OFFSET); \
> +#define DACDelay(hw) \
> + do { \
> + (hw)->readST01((hw)); \
> + (hw)->readST01((hw)); \
> } while (0)
>
> /* Function Prototypes */
Will try it tomorrow when I get to the office.
Thanks,
Jeff.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: X Segmentation fault with i810
On 1/3/12 1:00 PM, Adam Jackson wrote:
On 1/3/12 12:49 PM, Chris Wilson wrote:
On Tue, 03 Jan 2012 12:02:43 -0500, Adam Jackson wrote:
On 12/30/11 12:34 AM, Jeff Chua wrote:
How can I go about to help debug this?
The i810 driver probably needs the equivalent fix as:
http://cgit.freedesktop.org/xorg/driver/xf86-video-cirrus/commit/?id=f422d0c38b0befdb2152215ab05d0d14f3da3ed9
The i810 driver uses vgaHWSetMmioFuncs() rather than SetStdFuncs, and so
leaves hwp->io uninitialised. That pointer is then dereferenced by
DACDelay() (as it uses pci_io_read8 irrespective of mmio/std funcs)
during
the vgaHWSaveColormap(). At which point, I'm far beyond my comfort
zone...
-Chris
Oof, okay, nice find. DACDelay needs to not do that, or at least, not
unconditionally. I'll look into it.
Something like this?
---
diff --git a/hw/xfree86/vgahw/vgaHW.h b/hw/xfree86/vgahw/vgaHW.h
index e943aa3..9fa8183 100644
--- a/hw/xfree86/vgahw/vgaHW.h
+++ b/hw/xfree86/vgahw/vgaHW.h
@@ -170,10 +170,10 @@ typedef struct _vgaHWRec {
#define BITS_PER_GUN 6
#define COLORMAP_SIZE 256
-#define DACDelay(hw)\
- do { \
- pci_io_read8((hw)->io, (hw)->IOBase + VGA_IN_STAT_1_OFFSET); \
- pci_io_read8((hw)->io, (hw)->IOBase + VGA_IN_STAT_1_OFFSET); \
+#define DACDelay(hw) \
+ do {\
+ (hw)->readST01((hw)); \
+ (hw)->readST01((hw)); \
} while (0)
/* Function Prototypes */
---
- ajax
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
Re: X Segmentation fault with i810
On 1/3/12 12:49 PM, Chris Wilson wrote: On Tue, 03 Jan 2012 12:02:43 -0500, Adam Jackson wrote: On 12/30/11 12:34 AM, Jeff Chua wrote: How can I go about to help debug this? The i810 driver probably needs the equivalent fix as: http://cgit.freedesktop.org/xorg/driver/xf86-video-cirrus/commit/?id=f422d0c38b0befdb2152215ab05d0d14f3da3ed9 The i810 driver uses vgaHWSetMmioFuncs() rather than SetStdFuncs, and so leaves hwp->io uninitialised. That pointer is then dereferenced by DACDelay() (as it uses pci_io_read8 irrespective of mmio/std funcs) during the vgaHWSaveColormap(). At which point, I'm far beyond my comfort zone... -Chris Oof, okay, nice find. DACDelay needs to not do that, or at least, not unconditionally. I'll look into it. - ajax ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: X Segmentation fault with i810
On Tue, 03 Jan 2012 12:02:43 -0500, Adam Jackson wrote: > On 12/30/11 12:34 AM, Jeff Chua wrote: > > > How can I go about to help debug this? > > The i810 driver probably needs the equivalent fix as: > > http://cgit.freedesktop.org/xorg/driver/xf86-video-cirrus/commit/?id=f422d0c38b0befdb2152215ab05d0d14f3da3ed9 The i810 driver uses vgaHWSetMmioFuncs() rather than SetStdFuncs, and so leaves hwp->io uninitialised. That pointer is then dereferenced by DACDelay() (as it uses pci_io_read8 irrespective of mmio/std funcs) during the vgaHWSaveColormap(). At which point, I'm far beyond my comfort zone... -Chris -- Chris Wilson, Intel Open Source Technology Centre ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Re: X Segmentation fault with i810
On 12/30/11 12:34 AM, Jeff Chua wrote: How can I go about to help debug this? The i810 driver probably needs the equivalent fix as: http://cgit.freedesktop.org/xorg/driver/xf86-video-cirrus/commit/?id=f422d0c38b0befdb2152215ab05d0d14f3da3ed9 - ajax ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
