public inbox for
help / color / mirror / Atom feed
From: Jon TURNEY <>
To: cygwin-xfree <>
Subject: Re: segfault Xserver...current version (1.10, not 1.8)
Date: Wed, 10 Aug 2011 14:41:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 09/08/2011 00:39, Linda Walsh wrote:
>>> 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.

I am fully aware of these issues.

Unfortunately, the cygwin packaging tools don't currently allow me to detach, 
preserve and distribute the debug symbols, so a backtrace on the distributed 
binary is of little use as (i) it isn't annotated with symbols and (ii) I 
don't have the debug symbols, so I can't retrace the backtrace to annotate it 
with symbols.

> That said, I suppose I don't care that much, other than to get the problem
> fixed at some 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)...

You can use the cygwin dumper tool [1] to produce a core dump, but this is not 
very useful on the stripped binary, for the reasons given above.


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

Volunteer Cygwin/X X Server maintainer

Unsubscribe info:
Problem reports:

  reply	other threads:[~2011-08-10 14:41 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
2011-08-10 14:41         ` Jon TURNEY [this message]
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:

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

  git send-email \ \ \ \ \

* 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).