public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Linda Walsh <cygwin@tlinx.org>
To: cygwin-xfree@cygwin.com
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: segfault Xserver...current version (1.10, not 1.8)
Date: Mon, 08 Aug 2011 23:40:00 -0000	[thread overview]
Message-ID: <4E4073CB.6020502@tlinx.org> (raw)
In-Reply-To: <4E3FD322.2040804@dronecode.org.uk>

Jon TURNEY wrote:.
> 
> Does this mean that the xorg-server version reported by cygcheck is 
> incorrect because you've installed the tar file by hand?
---
	apparently.
> 
> I just cannot understand how you could paste your cygcheck.out, but not 
> mention that important fact.
----
	I cannot understand how you cannot understand that I'd have no inherent
clue how cygcheck would work or fail -- and that by taking a 
cygwin-setup tar image
from it's setup dir, and installing it by hand, and then 'hand-calling' 
it's "post-install
script", wouldn't update the versions for cygcheck.  I was surprised 
when you highlighted
the wrong version.

	I did run the post-install scripts for the package.  Perhaps it they 
need to
call some common update routine that didn't get called to update the 
version?

	Sounds like a case of the tar and post-install scripts expecting things 
to be
done, that are not clearly spelled out anywhere.   So, how would would 
you have expected
me to know that?  Magic?  It's not like I've had to do it before.   Just 
that setup
is broken -- and won't install single packages without alot of effort 
(as at least one other
person posted!),


	So please be aware, I didn't know that cygcheck relied on some 
private-static
database may have little to do with the actual system (files could have 
been restore, as
well -- in fact WERE!...in the /bin dir, when nothing worked, I guess I 
thought
cygcheck looked at version numbers in the binaries...but ... well silly 
me (hey,
if it was something I relied on, I'd want it to tell me what the actual 
binaries are,
not just what some static db thinks they are...but...that's me, and I'm 
used to things not
always being the way the 'should' be...(so you have to program for the 
unexpected!)...

> 
> Also, don't do that, it's not supported.
---
	Installing single packages is supposed to be supported, it's broken.
What is the workaround?


> 
>> Regarding a stack traceback -- I dont' see where the Xserver has produced
>> a corefile to run gdb on (???). Does it produce one?
> 
> No.
---
	Oh.   I try to config most of my apps to generate core dumps so I can
get tracebacks of the actual problem that occurred in the actual binary 
that it
occurred in.

	The instructions below don't say anything about getting a stack backtrace
for the binary I'm running.   They talk about downloading a different 
binary that
may not reproduce the problem.  In which case, I don't know if the 
problem is solved,
or something just didn't step on something, randomly in memory due to 
some flailing pointer.

	Anytime you substitute a binary, getting a stacktrace or trying to 
produce a problem
becomes an iffy proposition, because you aren't using the same program.

	That said, I suppose I don't care that much, other than to get the problem
fixed at some point...so when I get time, I'll move forward with trying 
the instructions
below...
Which, BTW, I had already read before I asked about the coredumps for 
the current binary --
(I'd like to know how to enable coredumps for the current binary! not a 
different one, but
that may not be possible -- you might think about being able enable it 
in the future based
on some ENV setting...just a thought)...

> As I said once already:
---
Yes you did, but that wasn't my question -- all I asked was about core 
dumps for the current
binary.  I didn't say I wouldn't do the below -- nor did I say the below 
told me to use
the core dumps from my current binary...  It was a related question, but 
not about how to do
the 'below'...sorry if that was confusing...




> 
>> Following the instructions at [2] to obtain an Xserver backtrace would 
>> also be of great help.
> 
> [2] http://x.cygwin.com/devel/backtrace.html
> 

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


  reply	other threads:[~2011-08-08 23:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05  0:04 segfault Xserver...current version (1.8) Linda Walsh
2011-08-06 15:57 ` Jon TURNEY
2011-08-06 18:01   ` Linda Walsh
2011-08-07 11:26     ` Csaba Raduly
2011-08-08  6:37       ` Linda Walsh
2011-08-08 12:15     ` segfault Xserver...current version (1.10, not 1.8) Jon TURNEY
2011-08-08 23:40       ` Linda Walsh [this message]
2011-08-10 14:41         ` Jon TURNEY
2011-08-10  0:55       ` Linda Walsh
2011-08-10  5:11         ` Christopher Faylor
2011-08-16  7:16           ` Linda Walsh
2011-08-16 12:28             ` Jon TURNEY

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E4073CB.6020502@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=cygwin-xfree@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).