public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: ioctl crash in mpg123
Date: Fri, 02 May 2014 15:15:00 -0000	[thread overview]
Message-ID: <20140502151500.GA632@ednor.casa.cgf.cx> (raw)
In-Reply-To: <53637E89.2060404@gmail.com>

On Fri, May 02, 2014 at 07:16:25PM +0800, JonY wrote:
>Hi,
>
>I am debugging a crash in Cygwin 1.7.29-2 ioctl but I am not familiar
>with the OSS sounds API. I traced the ioctl calls and made this example,
>is it supposed to work?

If you're asking if Cygwin is supposed to SEGV in certain situations the
answer is "no".

This should be fixed in the next snapshot.

Thanks for the test case.

cgf

--
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:[~2014-05-02 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 11:16 JonY
2014-05-02 15:15 ` Christopher Faylor [this message]
2014-05-03  0:14   ` JonY

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=20140502151500.GA632@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@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).