public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Axel Heinrici" <DerAxel@gmx.de>
To: cygwin@cygwin.com
Subject: Re: ImageMagick is crashing
Date: Wed, 31 May 2017 09:06:00 -0000	[thread overview]
Message-ID: <trinity-b6101ee7-7058-4ff7-acf0-f8217a39983f-1496213780106@3capp-gmx-bs46> (raw)
In-Reply-To: <e3fc4805-8f04-3f6d-fe77-17327a4785ab@gmail.com>

Hello,
 
strace doesn't seem to work either.

$ strace convert z06.png  z06.jpg
      0 [main] strace 8996 C:\cygwin64\bin\strace.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small: 50.
   1341 [main] strace 8996 cygwin_exception::open_stackdumpfile: Dumping stack trace to strace.exe.stackdump

And even more surprising
$ strace.exe ls
      0 [main] strace 1916 C:\cygwin64\bin\strace.exe: *** fatal error - Internal error: TP_NUM_W_BUFS too small: 50.
   1231 [main] strace 1916 cygwin_exception::open_stackdumpfile: Dumping stack trace to strace.exe.stackdump

Best regards,
    Axel
 

Gesendet: Mittwoch, 31. Mai 2017 um 06:59 Uhr
Von: "Marco Atzeri" <marco.atzeri@gmail.com>
An: "Axel Heinrici" <DerAxel@gmx.de>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Betreff: Re: ImageMagick is crashing
On 30/05/2017 15:26, Axel Heinrici wrote:
> Hello,
>
> the question remains, what is going wrong on my machine.
>
> Best regards,
> Axel
>

I have no idea.
Can you try to run with strace to see where is segfaulting ?

--
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:[~2017-05-31  6:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30  9:36 Axel Heinrici
2017-05-30 13:50 ` Marco Atzeri
2017-05-30 14:35   ` Axel Heinrici
2017-05-31  7:10     ` Marco Atzeri
2017-05-31  9:37       ` Axel Heinrici
     [not found]   ` <trinity-69616ed4-6c82-4c2a-8605-5584593d8475-1496136827030@3capp-gmx-bs74>
     [not found]     ` <d34df919-5697-f1a4-8764-d78a91d5ce50@gmail.com>
     [not found]       ` <trinity-a9579b37-0af3-486e-bd61-84a76b6a957b-1496150771191@3capp-gmx-bs74>
2017-05-31  5:46         ` Marco Atzeri
2017-05-31  9:06           ` Axel Heinrici [this message]
2017-05-31 13:26             ` Marco Atzeri

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=trinity-b6101ee7-7058-4ff7-acf0-f8217a39983f-1496213780106@3capp-gmx-bs46 \
    --to=deraxel@gmx.de \
    --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).