From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Vim segv'ing
Date: Fri, 01 Jul 2011 09:44:00 -0000 [thread overview]
Message-ID: <20110701094339.GO9552@calimero.vinschen.de> (raw)
In-Reply-To: <20110701083603.GM9552@calimero.vinschen.de>
On Jul 1 10:36, Corinna Vinschen wrote:
> FYI, I tracked it down to the place where the stack overwrite occurs.
> This is most puzzeling. When typing :wq!, the following chain of functions
> is called:
>
> nv_colon
> do_cmdline
> ex_exit
> do_write
> open <- Here it calls into the Cygwin DLL
> fhandler_base::open_with_arch
> fhandler_base::open_fs
> fhandler_base::open
> NtCreateFile <--Here it calls into NTDLL.DLL
>
> The open call tries to open the backup file "/etc/hosts~", not the
> symlink itself.
>
> In the optimized version of vim, the local variable "cap" in the
> function nv_colon is kept in register $esi. When do_cmdline is called,
> $esi is pushed onto the stack. Then everything goes its normal ways,
> until NtCreateFile is called.
>
> And here's the puzzler: This call to NtCreateFile overwrites the 4 byte
> stack slot in which the "cap" pointer is saved with the value 0x10c!
> [...]
> Oh, and here's a last-minute surprise: It does not happen if you run
> gvim, rather than vim. Maybe I should just give up to provide packages.
And it also does not happen if I build Cygwin with gcc 4.5.1 rather than
with gcc 4.3.4. Is it possible that a compiler bug is playing a role
here? I can't quite believe it, the effect is too specific.
Corinna
P.S.: Yaakov, is there any chance to get a 4.5.3 x86_64 cross compiler
package? Yum always tries to replace my x86_64 4.5.1 package with the
4.5.3 package for i686, but that doesn't work due to missing
dependencies...
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader 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
next prev parent reply other threads:[~2011-07-01 9:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 19:35 Andrew DeFaria
2011-06-29 22:28 ` Jeremy Hetzler
2011-06-29 22:43 ` Jeremy Hetzler
2011-06-30 7:20 ` Corinna Vinschen
2011-06-30 12:32 ` Nellis, Kenneth
2011-06-30 14:24 ` Corinna Vinschen
2011-06-30 15:05 ` Corinna Vinschen
2011-07-01 8:36 ` Corinna Vinschen
2011-07-01 9:44 ` Corinna Vinschen [this message]
2011-07-01 10:09 ` Yaakov Selkowitz
2011-07-01 10:21 ` Corinna Vinschen
2011-07-01 10:21 ` Andy Koppe
2011-07-01 11:44 ` Corinna Vinschen
2011-07-01 19:36 ` Chris Sutcliffe
2011-07-02 5:31 ` Charles Wilson
2011-07-02 23:49 ` Christopher Faylor
2011-07-04 22:29 ` Yaakov (Cygwin/X)
2011-07-05 9:10 ` Corinna Vinschen
2011-07-06 8:28 ` Yaakov (Cygwin/X)
2011-07-06 8:53 ` Corinna Vinschen
2011-06-30 20:09 ` Warren Young
2011-07-01 1:43 ` Chris Sutcliffe
2011-07-01 8:37 ` Corinna Vinschen
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=20110701094339.GO9552@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).