From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: cygwin64 info.exe Exception: STATUS_ACCESS_VIOLATION if no info file found
Date: Thu, 31 Oct 2013 21:17:00 -0000 [thread overview]
Message-ID: <loom.20131031T214224-280@post.gmane.org> (raw)
cygwin64 info.exe consistently dumps when no info file is found - whether or
not there is a man page.
cygwin32 works as always, displaying a man page if found, or status line
message "No menu item `zzzz' in node `(dir)Top'."
Running under gdb where there is a man page but no info file:
Reading symbols from /usr/bin/info...(no debugging symbols found)...done.
(gdb) run sntp
Starting program: /usr/bin/info sntp
[New Thread 1876.0x41c]
[New Thread 1876.0x19a8]
Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x000007fefd6710dc in WaitForSingleObjectEx () from
/cygdrive/c/Windows/system32/KERNELBASE.dll
#2 0x0000000600000001 in ?? ()
#3 0x0000000000000000 in ?? ()
(gdb) return
Make selected stack frame return now? (y or n) y
#0 0x000007fefd6710dc in WaitForSingleObjectEx ()
from /cygdrive/c/Windows/system32/KERNELBASE.dll
(gdb) cont
Continuing.
0 [main] info 1876 open_stackdumpfile: Dumping stack trace to
info.exe.stackdump
[Inferior 1 (process 1876) exited with code 0105400]
(gdb) q
Stackdumps:
gdb run sntp
Exception: STATUS_ACCESS_VIOLATION at rip=00180168EBD
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=FEFEFEFF0F030100 rsi=0000000000000004 rdi=00000006000487B0
r8 =FFFFFFFF8F8B918C r9 =8080808080808080 r10=FEFEFEFEFEFEFEFF
r11=00000006000487B0 r12=0000000000000005 r13=00000006000487B0
r14=00000006000486B0 r15=00000006000493A0
rbp=000000000000000C rsp=000000000022A448
program=C:\usr\local\cygwin64\bin\info.exe, pid 1876, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
info sntp
Exception: STATUS_ACCESS_VIOLATION at rip=00180168EBD
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=FEFEFEFF0F030100 rsi=0000000000000004 rdi=0000000600048970
r8 =FFFFFFFF8F8B918C r9 =8080808080808080 r10=FEFEFEFEFEFEFEFF
r11=0000000600048970 r12=0000000000000005 r13=0000000600048970
r14=0000000600048870 r15=0000000600047AA0
rbp=000000000000000C rsp=000000000022A488
program=C:\usr\local\cygwin64\bin\info.exe, pid 4548, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
info zzzz
Exception: STATUS_ACCESS_VIOLATION at rip=00180168EBD
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=FEFEFEFF01010101 rsi=0000000000000004 rdi=0000000600048970
r8 =FFFFFFFF85858585 r9 =8080808080808080 r10=FEFEFEFEFEFEFEFF
r11=0000000600048970 r12=0000000000000005 r13=0000000600048970
r14=0000000600048870 r15=0000000600047AA0
rbp=000000000000000C rsp=000000000022A488
program=C:\usr\local\cygwin64\bin\info.exe, pid 7896, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Next steps?
--
Take care. Thanks, Brian Inglis
--
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
next reply other threads:[~2013-10-31 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 21:17 Brian Inglis [this message]
2013-11-05 19:27 ` Brian Inglis
2013-11-06 8:53 ` Csaba Raduly
2013-11-07 20:25 ` Brian Inglis
2013-11-09 10:42 ` Brian Inglis
2013-11-09 10:47 ` Corinna Vinschen
2013-11-09 11:38 ` Brian Inglis
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=loom.20131031T214224-280@post.gmane.org \
--to=brian.inglis@systematicsw.ab.ca \
--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).