This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: xterm access violations (again)
- From: Jon TURNEY <jon dot turney at dronecode dot org dot uk>
- To: cygwin-xfree <cygwin-xfree at cygwin dot com>
- Date: Mon, 04 Apr 2011 14:27:27 +0100
- Subject: Re: xterm access violations (again)
- References: <20110322165117.N24352@mail101.his.com> <AANLkTinLp9rwYYpYa=iCN93yxfsU_4__EZDah_+TJD5x@mail.gmail.com> <20110323171230.G30377@mail101.his.com> <AANLkTimUtBwq4TQqm4ZLpZYeSEi04=8s-KFxHO4P8u4m@mail.gmail.com> <1300929672.316.17.camel@YAAKOV04> <AANLkTi=HHpsXkNL+Xeb3rhiQAvpZ+ogewiiUD1bGeYYE@mail.gmail.com> <AANLkTi=53FmJfzHmByLmMUrs2cr-WOmy29pB+UbAsfGb@mail.gmail.com> <AANLkTikikSeWi51B2nd7CbQuBfct8bYoCcD=Ub64e1yK@mail.gmail.com> <AANLkTinYRa0usi9p_FAZE1=iv_+ypTpMOAmtRGjmsYtV@mail.gmail.com> <20110325052241.GA18053@ednor.casa.cgf.cx> <20110326183523.GA30114@ednor.casa.cgf.cx> <AANLkTi=aqZPU+Q-TinAByNEhiaXusyBVqZuTE+gmNjbO@mail.gmail.com> <AANLkTi=rzkT0F=C-FTqDx=MHwvxoMrfgZ8D9iaB4Peb2@mail.gmail.com>
- Reply-to: cygwin-xfree at cygwin dot com
On 01/04/2011 17:05, Jim Reisert AD1C wrote:
> On Sun, Mar 27, 2011 at 1:50 PM, Jim Reisert AD1C wrote:
>> On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote:
>>> Could someone try this with the latest snapshot? I haven't made any
>>> changes but I just want to confirm that it still fails with something
>>> close to what will become Cygwin 1.7.9.
>>>
>>> http://cygwin.com/snapshots/
>>>
>>> You just have to replace the DLL. Don't bother with a "cygwin-inst*"
>>> tarball.
>>
>> Yes, still there:
>
> How can I/we assist in debugging this problem? First we need to
> determine where the problem lies, whether it's in Cygwin itself, or
> xterm. Today it took me 3-4 tries to get an xterm up. As I was
> running late for work, it was kind of frustrating.
I think you could:
1. Obtain the cygwin1.dbg file corresponding to your cygwin1.dll (for
snapshots, it is available from the snapshot page, for releases, I believe it
is in the corresponding cygwin src package), and place it next to your cygwin1.dll
2. Run xterm under gdb
3. Obtain a backtrace when the segv occurs
4. Diagnose the problem
5. Write and test a patch to fix it
You'll probably want to refer to [1] for that last step. :-)
[1] http://cygwin.com/contrib.html
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/