From: Paul Eggert <eggert@cs.ucla.edu>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 34174@debbugs.gnu.org
Subject: bug#34174: 27.0.50; Calling `par' via shell-command-on-region always errors out
Date: Wed, 23 Jan 2019 10:05:44 -0800 [thread overview]
Message-ID: <c43744e5-f543-b80f-5ffa-4abb73b8d212@cs.ucla.edu> (raw)
In-Reply-To: <CAFyQvY2Y4kZkYA_t8etCoJgPeZvFs5NMo3dTqV8FuBipNePvGQ@mail.gmail.com>
On 1/23/19 9:37 AM, Kaushal Modi wrote:
> I ran:
>
> strace -o /tmp/par.tr <http://par.tr> par, and
> strace -o /tmp/emacs.tr <http://emacs.tr> emacs -Q
>
> Looking at the .tr files, they could possibly contain work sensitive
> data. So I am not sure if I should share those files publicly.
We care about the I/O requests involving the text you're reformatting,
so I suggest running 'par' on some innocuous text and just looking at
the associated syscalls (assuming you can reproduce the problem).
Also, please try running the shell command 'fmt' on the same text, to
see if that can reproduce the problem. If it doesn't reproduce the
problem, see how fmt's system calls differ from par's. I mention 'fmt'
because it's similar to 'par' and I can easily run 'fmt' here.
> [ So the problem, as you guessed, seems to be with my OS (RHEL 6.8) ..
> But why only `par`? hmm ]
Wow, that's older than even the most-ancient RHEL host I have ready
access to (RHEL 6.10). I could not reproduce the problem on that host,
using 'fmt'.
next prev parent reply other threads:[~2019-01-23 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 22:27 bug#34174: 27.0.50; Calling `par' via shell-command-on-region always errors out Kaushal Modi
2019-01-23 17:29 ` Paul Eggert
2019-01-23 17:37 ` Kaushal Modi
2019-01-23 18:05 ` Paul Eggert [this message]
2019-01-29 2:29 ` Kaushal Modi
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c43744e5-f543-b80f-5ffa-4abb73b8d212@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=34174@debbugs.gnu.org \
--cc=kaushal.modi@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).