Re: segfault Xserver...current version (1.8)

2011-08-08 Thread Linda Walsh

Csaba Raduly wrote:

On Sat, Aug 6, 2011 at 8:01 PM, Linda Walsh  wrote:

Jon TURNEY wrote:

(snip)

Next time, please *attach* the *full* XWin.0.log

---
   That was the full log...it had been truncated -- perhaps by the
failing
processes...A full log from a non-crashed version (i.e. I haven't run
yast2), is here:


To attach is to use File-Attach-File... or click the paperclip
icon, as opposed to pasting the log into the body of the message.


Ah...I focused on the 'full' part, not the attached part.

It's just damn confusing.

One list, filters attachments, another, they expect it...
ARG!



Also, please set Thunderbird to attach files correctly:

---
Don't worry, Have done so in the past, forgot that this list
*wants* them as attachments (vs. some others lists where such will be
automatically stripped)...



http://blog.crox.net/archives/23-How-to-set-thunderbird-to-correctly-attach-text-files-with-Content-Disposition-attachment-instead-of-inline.html


   Yeah -- that's why I don't like to include cygcheck.out's
They give out lots of info that isn't _entirely_ relevant.  It's not even an
accurate package listing if one has installed packages w/tar by hand.


What you deem relevant may not match what others on this list deem
relevant. You might omit information that would have helped diagnosing
your problem.
There's a reason for what's written in

Problem reports:   http://cygwin.com/problems.html

---
There are reasons for everything we come up with.
That doesn't mean they are _always_ good reasons.

Note I did try to underline the word entirely, AND, I did include
it, whatever my reservations.  I was merely commenting on how, in some
cases it provides 'random goose chase' information.  More often than
not, I've seen it used to blow off user bug reports because some i isn't
dotted, or t, crossed.  Whatever, I understand, which isn't to say I
always necessarily enjoy it -- but in this circumstance, considering
the abstractions and mixtures of SW, I thought such a report more than
reasonable to provide.

I'm just wondering if there's a way to turn on coredumps and give stack
traces of the X I'm running vs. downloading some 'extra special' version.
I get coredumps on linux and windows, and am able to generate backtrace info
on both for many situations (more on linux than windows), sometimes it 
leads me

to investigate things more on my own and even find workaround or fixes,
but the X server hasn't crashed on me since the last report, (but I am 
steering

away from running yast2 for the time being!)




C'est la vie  Cheers!
Linda



--
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/



Re: segfault Xserver...current version (1.8)

2011-08-07 Thread Csaba Raduly
On Sat, Aug 6, 2011 at 8:01 PM, Linda Walsh  wrote:
 Jon TURNEY wrote:
(snip)
 Next time, please *attach* the *full* XWin.0.log

 ---
        That was the full log...it had been truncated -- perhaps by the
 failing
 processes...A full log from a non-crashed version (i.e. I haven't run
 yast2), is here:

To attach is to use File-Attach-File... or click the paperclip
icon, as opposed to pasting the log into the body of the message.

Also, please set Thunderbird to attach files correctly:
http://blog.crox.net/archives/23-How-to-set-thunderbird-to-correctly-attach-text-files-with-Content-Disposition-attachment-instead-of-inline.html

        Yeah -- that's why I don't like to include cygcheck.out's
 They give out lots of info that isn't _entirely_ relevant.  It's not even an
 accurate package listing if one has installed packages w/tar by hand.

What you deem relevant may not match what others on this list deem
relevant. You might omit information that would have helped diagnosing
your problem.
There's a reason for what's written in

Problem reports:   http://cygwin.com/problems.html


Csaba
-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
Ok, it boots. Which means it must be bug-free and perfect.  -- Linus Torvalds
People disagree with me. I just ignore them. -- Linus Torvalds

--
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/



Re: segfault Xserver...current version (1.8)

2011-08-06 Thread Jon TURNEY

On 05/08/2011 01:02, Linda Walsh wrote:

/var/log/XWin more XWin.0.log
[ 58452.716] winInitMultiWindowWM - XOpenDisplay () returned and successfully op
ened the display.
[ 58452.716] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully
opened the display.
[ 58452.732] winClipboardProc - XOpenDisplay () returned and successfully opened
the display.
[ 58458.145] Segmentation fault at address 0x0
[ 58458.145]
Fatal server error:
[ 58458.145] Caught signal 11 (Segmentation fault). Server aborting
[ 58458.145]
~
~

I just upgraded to the new server last night...


1.8.0-1 is not the current version, 1.10.3-1 is (See [1]).

Next time, please *attach* the *full* XWin.0.log


Works fine for most things...

But ran yast2, on my suse box kills it every time. w/signal 11.


If this is still reproducible when you've upgraded to the current version of 
the Xserver, can you tell me what SuSE version you are using, please?


Following the instructions at [2] to obtain an Xserver backtrace would also be 
of great help.



Previous version didn't have a problem.


'Previous' is not a number.


cygcheck.out:

[snip]

xorg-server 1.8.0-1 OK

[snip]

[1] http://cygwin.com/ml/cygwin-xfree-announce/2011-07/msg1.html
[2] http://x.cygwin.com/devel/backtrace.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/



Re: segfault Xserver...current version (1.8)

2011-08-06 Thread Linda Walsh

Jon TURNEY wrote:

On 05/08/2011 01:02, Linda Walsh wrote:

/var/log/XWin more XWin.0.log
[ 58452.716] winInitMultiWindowWM - XOpenDisplay () returned and 
successfully op

ened the display.
[ 58452.716] winMultiWindowXMsgProc - XOpenDisplay () returned and 
successfully

opened the display.
[ 58452.732] winClipboardProc - XOpenDisplay () returned and 
successfully opened

the display.
[ 58458.145] Segmentation fault at address 0x0
[ 58458.145]
Fatal server error:
[ 58458.145] Caught signal 11 (Segmentation fault). Server aborting
[ 58458.145]
~
~

I just upgraded to the new server last night... 

Next time, please *attach* the *full* XWin.0.log

---
That was the full log...it had been truncated -- perhaps by the failing
processes...A full log from a non-crashed version (i.e. I haven't run 
yast2), is here:


/var/log/XWin more XWin.0.log
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.10.3.0
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64)
Package: version 1.10.3-1 built 2011-07-19

XWin was started with the following command line:

/usr/bin/XWin -dpi 101 -multiwindow -clipboard -nowinkill -wm

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 2560 h 1600
winInitializeDefaultScreens - native DPI x 120 y 120
[   938.034] (II) xorg.conf is not supported
[   938.034] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for 
more in

formation
[   938.034] LoadPreferences: Loading //Bliss/law/.XWinrc
[   938.049] LoadPreferences: Done parsing the configuration file...
[   938.190] winDetectSupportedEngines - DirectDraw installed, allowing 
ShadowDD

[   938.190] winDetectSupportedEngines - Windows NT, allowing PrimaryDD
[   938.190] winDetectSupportedEngines - DirectDraw4 installed, allowing 
ShadowD

DNL
[   938.221] winDetectSupportedEngines - Returning, supported engines 
001f

[   938.221] winSetEngine - Multi Window or Rootless = ShadowGDI
[   938.221] winScreenInit - Using Windows display depth of 32 bits per 
pixel
[   938.221] winAllocateFBShadowGDI - Creating DIB with width: 4480 
height: 1600

 depth: 32
[   938.221] winFinishScreenInitFB - Masks: 00ff ff00 00ff
[   938.221] winInitVisualsShadowGDI - Masks 00ff ff00 00ff 
BPRGB 8

d 24 bpp 32
[   938.221] winInitMultiWindowWM - Calling pthread_mutex_lock ()
[   938.221] winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
[   938.221] Screen 0 added at virtual desktop coordinate (0,0).
[   938.283] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
[   938.283] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[   938.642] winPointerWarpCursor - Discarding first warp: 2240 800
[   938.642] (--) 7 mouse buttons found
[   938.642] (--) Setting autorepeat to delay=250, rate=31
[   938.642] (--) Windows keyboard layout: 0409 (0409) US, 
type 4

[   938.642] (--) Found matching XKB configuration English (USA)
[   938.642] (--) Model = pc105 Layout = us Variant = none Options 
= none


[   938.642] Rules = base Model = pc105 Layout = us Variant = 
none Optio

ns = none
[   938.642] winBlockHandler - pthread_mutex_unlock()
[   938.642] winInitMultiWindowWM - pthread_mutex_lock () returned.
[   938.642] winInitMultiWindowWM - pthread_mutex_unlock () returned.
[   938.642] winMultiWindowXMsgProc - pthread_mutex_lock () returned.
[   938.642] winInitMultiWindowWM - DISPLAY=:0.0
[   938.642] winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
[   938.642] winProcEstablishConnection - winInitClipboard returned.
[   938.642] winMultiWindowXMsgProc - DISPLAY=:0.0
[   938.642] winClipboardProc - DISPLAY=:0.0
[   938.642] winInitMultiWindowWM - XOpenDisplay () returned and 
successfully op

ened the display.
[   938.658] winMultiWindowXMsgProc - XOpenDisplay () returned and 
successfully

opened the display.
[   938.673] winClipboardProc - XOpenDisplay () returned and 
successfully opened

 the display.
[  4096.679] OS has icon alpha channel support: yes

---


1.8.0-1 is not the current version, 1.10.3-1 is (See [1]).


I'm running 1.10.3.1 as you can see from the full log...

I will now crash my xserver...

[duplicate portions of above log suppressed...exactly the same timestamps
up to [4096.679]].
[100813.992] Segmentation fault at address 0x0
[100813.992]
Fatal server error:
[100813.992] Caught signal 11 (Segmentation fault). Server aborting
[100813.992]
---

I've no idea why the original log was truncated 'funny', other than I'd
tried to start and had crashed the server several times in a row,
so it's possible in the multiple invocations one log overwrote another.








Works fine for most things...

But ran yast2, on my suse box kills it every time. w/signal 11.


If this is still reproducible when you've upgraded to the current 
version of the Xserver, can you tell me what SuSE version you are using, 
please?


Suse 11.4
Ishtar: rpm -qa|grep  -P