public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ViOLeT <archguru1004@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin 2.9.0 regtool x64 exception error (W10)
Date: Wed, 29 Nov 2017 15:41:00 -0000	[thread overview]
Message-ID: <CA++AZfvR9Sedau8rhmmUFG3yn0P--=PfkxyfhA-Qh+vps8rCQw@mail.gmail.com> (raw)
In-Reply-To: <20171129092922.GV547@calimero.vinschen.de>

# OS Language
Korean (Asia), CHCP Code 949

# Locale Code
LANG=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_ALL=

Is it an operating system language issue?

2017-11-29 18:29 GMT+09:00 Corinna Vinschen <corinna-cygwin@cygwin.com>:
> Hi ViOLeT,
>
> On Nov 29 15:33, ViOLeT wrote:
>> Hello.
>>
>> Cygwin 2.9.0 regtool x64 exception error (W10) reporting. (But it seems to
>> be an error in all (2.9.0 lower) versions.)
>>
>> Using the Unicode causes an exception error.
>> But, regtool x86 is no error occurs.
>>
>> *Example :*
>> regtool.exe -w get "\HKCR\하하하"
>> regtool.exe -w get "\HKCR\家"
>>
>> *Exception Code : *
>> Exception: STATUS_ACCESS_VIOLATION at rip=00100401623
>> rax=0000000000000000 rbx=00000000FFFFFFFF rcx=0000000180201FC0
>> rdx=00000006000284E0 rsi=00000000FFFFFFFF rdi=00000006000284D0
>> r8 =0000000000000000 r9 =0000000000000020 r10=0000000100000000
>> r11=00000001004015E0 r12=0000000000000002 r13=00000000FFFFCC5E
>> r14=0000000000000003 r15=00000001802193F0
>> rbp=00000000FFFFCB30 rsp=00000000FFFFCAB0
>> program=C:\x64\regtool.exe, pid 15244, thread main
>> cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
>> Stack trace:
>> Frame        Function    Args
>> 000FFFFCB30  00100401623 (00100020019, 04900000000, 001801891FA,
>> 000FFFFCC5E)
>> 000FFFFCB9C  00100402704 (00000000000, 000FFFFCC5E, 00000000030,
>> FF0700010302FF00)
>> 000FFFFCCB0  00180047BC2 (00000000000, 00000000000, 00000000000,
>> 00000000000)
>> 00000000000  00180045863 (00000000000, 00000000000, 00000000000,
>> 00000000000)
>> 000FFFFFFF0  00180045914 (00000000000, 00000000000, 00000000000,
>> 00000000000)
>> End of stack trace
>
> Unfortunately I can't reproduce this.  I tried both of your above
> example registry values, but in both cases I just get
>
>   Error (2): The system cannot find the file specified.
>
> As another test I created the above values in the registry, as
> REG_SZ with content == name and this works fine, too.
>
> Your stackdump indicates a crash in the function evaluating the
> command line argument, that is, "\HKCR\하하하" or "\HKCR\家".
>
> If so, I should see the same problem, unless the problem is a result of
> the locale you're using.  Can you please post the output of the `locale'
> command?
>
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat

--
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-11-29 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29  6:33 ViOLeT
2017-11-29  9:29 ` Corinna Vinschen
2017-11-29 15:41   ` ViOLeT [this message]
2017-11-29 16:15     ` Corinna Vinschen
2017-11-29 16:44       ` ViOLeT

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='CA++AZfvR9Sedau8rhmmUFG3yn0P--=PfkxyfhA-Qh+vps8rCQw@mail.gmail.com' \
    --to=archguru1004@gmail.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).