public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ht@inf.ed.ac.uk (Henry S. Thompson)
To: cygwin@cygwin.com
Subject: strace and sigprocmask
Date: Fri, 09 May 2014 12:56:00 -0000	[thread overview]
Message-ID: <f5bzjir5cx4.fsf@troutbeck.inf.ed.ac.uk> (raw)

Running on Windows 8.1, with 32-bit Cygwin v1.7.29.

I've taken straces of a problematic area of xemacs, tidied them, and
am trying to locate significant differences.

I'm seeing something I don't understand, which isn't causing a crash
so probably isn't significant, but I'd like to understand it better.

strace 1 has:
 [main] PID1  sigprocmask:  0   =   sigprocmask(2647444,   0xNULL, 0xNULL)
where strace 2 has:
 [main] PID1  sigprocmask:  0   =   sigprocmask(2649272,   0xNULL, 0xADDR)

Similar lines appear frequently in both straces.

Either I don't understand strace output, or this is bizarre -- the
first arg to sigprocmask should always be 0, 1 or 2, right?

I'd welcome any help in understanding how I should be reading this,
and more generally, how I could have found the answer to my question
myself.

Thanks,

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
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-09 12:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 12:56 Henry S. Thompson [this message]
2014-05-09 14:31 ` Christopher Faylor

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=f5bzjir5cx4.fsf@troutbeck.inf.ed.ac.uk \
    --to=ht@inf.ed.ac.uk \
    --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).