public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: gimp crashes due to libSDL1.2_0 problem
Date: Fri, 18 May 2018 23:59:00 -0000	[thread overview]
Message-ID: <b1d4905b-9447-dc8f-e63c-82965827b4af@cornell.edu> (raw)
In-Reply-To: <7b423c88-a5e0-e5a8-d680-38ddd297ab42@cygwin.com>

On 5/18/2018 4:49 PM, Yaakov Selkowitz wrote:
> On 2018-05-18 13:14, Ken Brown wrote:
>> gimp crashes for me during its initialization when it is querying 
>> plugins.  Running it under gdb shows that the crash occurs when gimp 
>> (via g_spawn_async) tries to fork a subprocess to run a plugin.
> 
> https://cygwin.com/faq/faq.html#faq.using.fixing-fork-failures

This doesn't seem like the standard kind of fork failure that's fixed by 
rebasing.  For one thing, I'm on 64-bit Cygwin.  For another thing, the 
error message doesn't refer to being unable to remap a DLL to the same 
address as in the parent.

In any case, I did a full rebase, which didn't help.  I also manually 
rebased the problematic DLL cygSDL-1-2-0.dll to an address below the 
previously lowest base address of a Cygwin DLL, and that didn't help either.

I think there's something else going on.  It would help if some other 
people would try to reproduce the problem.  [I assume you already tried.]

Ken



--
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:[~2018-05-18 23:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 19:44 Ken Brown
2018-05-18 20:50 ` Yaakov Selkowitz
2018-05-18 23:59   ` Ken Brown [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=b1d4905b-9447-dc8f-e63c-82965827b4af@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).