On Mon, 2007-02-12 at 11:41 +0100, Brice Goglin wrote:
> About 14 months ago, you reported a bug to the Debian BTS regarding a
> crash of Xemacs on a nVidia board, possibly caused by a bug in libX11.
> Did you reproduce this problem recently?
No, I haven't seen this in a while. I think it's OK
Hi,
About 14 months ago, you reported a bug to the Debian BTS regarding a
crash of Xemacs on a nVidia board, possibly caused by a bug in libX11.
Did you reproduce this problem recently? If not, I will close this bug
in the next weeks.
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
[EMAIL PROTECTED] writes:
> OK, see the backtrace with the dbg version of libx11-6 below. We now
> we know what xemacs passed, and where the libx11 died, and the error
> is "no such file or directory" . Looking at the source for that file
> (ChkIfEv.c) doesn't show any obvious (to me) place where
Stephen J. Turnbull writes:
> > "Ben" == Ben Wing <[EMAIL PROTECTED]> writes:
>
> Ben> the best way to know for sure is for you to compille XEmacs
> Ben> yourself, with debugging support.
>
> Also, Debian supplies -dbg packages for the X libraries, so you would
> be able to ge
Hi.
From: [EMAIL PROTECTED]
Subject: Re: Bug#343129: xemacs / libX11 / NVIDIA crashes on opteron under
kernel 2.6.14-2
Date: Wed, 14 Dec 2005 10:38:29 -0700
> In working to figure out debian bug 343129, which involves crashes in
> Xemacs, Ben Wing suggested compiling my own xemacs (2
> "Ben" == Ben Wing <[EMAIL PROTECTED]> writes:
Ben> the best way to know for sure is for you to compille XEmacs
Ben> yourself, with debugging support.
Also, Debian supplies -dbg packages for the X libraries, so you would
be able to get useful traces. You just use LD_LIBRARY_PATH (or
Ohura-san,
In working to figure out debian bug 343129, which involves crashes in
Xemacs, Ben Wing suggested compiling my own xemacs (21.4.18) for
debugging. When I do that, the crash goes away. I configured it with
--debug and --with-gnome. What other flags did you use to configure
the xemac
[EMAIL PROTECTED] wrote:
Ben Wing writes:
> do the backtraces always look like this or do they vary?
They are always in XCheckIfEvent, although how they get there varies,
e.g.
ok, that's expected, since there are many places that the QUIT macro
occurs and it's triggered asynchronously.
8 matches
Mail list logo