Subject: bug#25503: Fwd: sed bug report

From: Assaf Gordon <[email-masked]>
Date: Sun, 22 Jan 2017 15:45:38 -0500

Hello

> On Jan 21, 2017, at 04:38, 한승석(http://whria.net) <[email-masked]> wrote:

Thank you for the bug report.

I'd like to ask for few additional details:

> sed.exe takes 100% CPU (1 Thread) if the file include some special char.

Does it take 100% and never terminates, or just takes a very long time, or something else?

> Windows sed 4.2.1 (the lastest version)

sed 4.2.1 is very old (from 2009).
It is not even the previous version (sed 4.2.2 was released in 2012, and is the
most commonly installed version around).

Can you try to reproduce this with the latest sed, available here:
  http://download-mirror.savannah.gnu.org/releases/sed/sed-4.3.16-572d.tar.xz

This version is based on sed-4.3 (released on 2016-Dec-30)
with one crucial additional bug fix.

> Windows 10

There are several methods to run on windows,
can you elaborate how you've built and run sed ?
e.g.
is it under cygwin, or built with mingw, or MSVC,
or the new "bash for windows", or something else ?

Can you share the output of running
   file $(which sed)
   uname -a
(if you have these programs available)

Since the bug relates to multibyte characters,
which locale or codepage are you using?
Can you share the output of running 'locale' ?

thanks,
 - assaf