Re: Seg fault with XQuartz 2.6.0 (xorg-server 1.9.3)
Re: Seg fault with XQuartz 2.6.0 (xorg-server 1.9.3)
- Subject: Re: Seg fault with XQuartz 2.6.0 (xorg-server 1.9.3)
- From: Jeremy Huddleston <email@hidden>
- Date: Wed, 05 Jan 2011 10:14:59 -0800
You're getting a segfault in emacs itself. I'd recommend starting with the emacs developers.
Also, it looks like you're *NOT* using the XQuartz 2.6.0 libraries here, so try using those instead (/opt/X11 versus /usr/X11). If it works on Ubuntu, it might be the case that using a xcb-backed libX11 works around whatever bug you're hitting in an xtrans-backed libX11.
Also, a full crash log would be helpful. You can copy/paste the crash log or just find it in ~/Library/Logs/DiagnosticReports
On Jan 5, 2011, at 07:02, Giles Chamberlin wrote:
> I’m building the latest emacs from git (
> git://git.savannah.gnu.org/emacs.git) which runs fine on Ubuntu 10.10.
> Building and running the same version on OSX 10.6.5/Xquartz 2.6.0 is not so
> successful: I get a segmentation fault on start up.
>
> Running “gdb emacs” seems to point the finger at Xquartz:
>
> (gdb) run
> Starting program: /Users/gilecham/git-repos/emacs/src/emacs
> Reading symbols for shared libraries .+ [snip].... done
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
> 0x0000000100e6429d in _X11TransWrite ()
>
>
> Does anyone have any suggestions as to how I can resolve this?
>
> Giles
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list (email@hidden)
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden