public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin glade v3.20.3 crashing with a segment fault.
Date: Wed, 04 Sep 2019 16:59:00 -0000	[thread overview]
Message-ID: <b32454a6-4fa2-7baa-ca11-531ae2196b98@SystematicSw.ab.ca> (raw)
In-Reply-To: <em67c5979b-0717-4240-8f50-bc133715a675@str-c>

On 2019-09-03 05:00, tvonderhaar wrote:
> Has anyone gotten Cygwin glade v3.20.3 to run without it crashing with a segment
> fault. I got the latest updates to make sure it had not been fixed. No luck. The
> strace is very long. I had attached a 7z compressed version of it but my E-Mail
> was reject as too long at greater that 1MB even though it is actually 940kb. It
> is hard to believe that the overhead of this message is over 60kb.  The strace
> indicates to me that the program wrote outside of it writeable memory space.

Compressed binaries have to be encoded in attachments which expands the contents
by about 1/3.
Copy the strace output and delete all the standard startup before your program
gets going, then copy that and delete what you can that is irrelevant before the
segv, then check the size is less than 1MB, and attach.
If still too big, can you post it in a Github gist, on a Google drive, or other
external site you have access to?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2019-09-04 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03 11:00 tvonderhaar
2019-09-04 16:59 ` Brian Inglis [this message]

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=b32454a6-4fa2-7baa-ca11-531ae2196b98@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).