Please try the procedures described in the section
"If you encounter X protocol errors" in etc/DEBUG.
What do you see?
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
[EMAIL PROTECTED] writes:
> again, emacs dies in x_error_quitter:
>
> Breakpoint 3, x_error_quitter (display=0x8591e38, error=0xbfe939a8)
> at xterm.c:7859
> 7859 if (error->error_code == BadName)
This is yet another example of a X protocol error that shouldn't cause
Emacs to abort. In
Hello!
The code around this line is:
11740 if test "$HAVE_XFT" != no; then
11741 OLD_CFLAGS="$CPPFLAGS"
11742 OLD_CFLAGS="$CFLAGS"
11743 OLD_LIBS="$LIBS"
11744 CPPFLAGS="$CPPFLAGS $XFT_CFLAGS"
11745 CFLAGS="$CFLAGS
Thanks.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Emacs crashes every time for me when I do the following:
1) download http://dooglus.rincevent.net/random/file2.ppm.bz2 (157KB)
2) bunzip2 the file
3) C-x C-f file2.ppm RET
4) C-x C-v RET
Here's the backtrace I see:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -121970
Hi,
When configure is called --without-hesiod or --without-kerberos{,5} it
acts as if --with-{hesiod,kerberos,kerberos5} was used. This is not
expected behaviour, as things as --with{,out}-x work that way.
In GNU Emacs 22.0.95.1 (i686-pc-linux-gnu, GTK+ Version 2.10.9)
of 2007-03-16 on luna
Win
Chris Moore <[EMAIL PROTECTED]> writes:
> Emacs crashes every time for me when I do the following:
>
> 1) download http://dooglus.rincevent.net/random/file2.ppm.bz2 (157KB)
> 2) bunzip2 the file
> 3) C-x C-f file2.ppm RET
> 4) C-x C-v RET
I've fixed this. Thanks.
_
Peter Dyballa skrev:
> Hello!
>
> The code around this line is:
>
> 11740 if test "$HAVE_XFT" != no; then
> 11741OLD_CFLAGS="$CPPFLAGS"
> 11742OLD_CFLAGS="$CFLAGS"
> 11743OLD_LIBS="$LIBS"
> 11744CPPFLAGS="$CPPFLAGS $XFT_CFLAGS"
> 11745
Christian Faulhammer <[EMAIL PROTECTED]> writes:
> When configure is called --without-hesiod or --without-kerberos{,5} it
> acts as if --with-{hesiod,kerberos,kerberos5} was used. This is not
> expected behaviour, as things as --with{,out}-x work that way.
Thanks, I've checked in a fix.
_
