From: Jim Schneider <jim.schneider@dataflux.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: 1.7.9-1 dll::init() still causing STATUS_ACCESS_VIOLATION errors
Date: Wed, 30 Nov 2011 20:50:00 -0000 [thread overview]
Message-ID: <609C4401F424CD42A1FB3F9E26889B3E03E30E39E6@df-ex03.us.dataflux.com> (raw)
I updated today to 1.7.9-1 from an earlier install. Now, bash produces a series of dozens of exception lines like the following:
214713567 [main] bash 5368 exception::handle: Exception: STATUS_ACCESS_VIOLATION
214714267 [main] bash 5368 open_stackdumpfile: Dumping stack trace to bash.exe.stackdump
The contents of bash.exe.stackdump are:
Exception: STATUS_ACCESS_VIOLATION at eip=6102048B
eax=00C40308 ebx=6124545C ecx=75110F81 edx=003C51F8 esi=00000000 edi=0028F9F4
ebp=61020C00 esp=0028C7C4 program=C:\cygwin\bin\bash.exe, pid 1928, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
End of stack trace
The address 6102048B is associated with line 82 of winsup/cygwin/dll_init.cc, which is in dll::init():
/* Initialize an individual DLL */
int
dll::init ()
{
int ret = 1;
/* This should be a no-op. Why didn't we just import this variable? */
if (!p.envptr)
p.envptr = &__cygwin_environ;
else
*(p.envptr) = __cygwin_environ; /* This is line 82 */
/* Don't run constructors or the "main" if we've forked. */
if (!in_forkee)
{
/* global contructors */
p.run_ctors ();
/* entry point of dll (use main of per_process with null args...) */
if (p.main)
ret = p.main (0, 0, 0);
}
return ret;
}
The pointer p.envptr is tested before an attempt is made to use it, so it looks like it is getting garbage. Disassembling the function dll::init shows that the edx register is being used to hold the address. It's holding 003C51F8, just short of 240K before the base address of bash.
If I manage to run it down, I'll send a patch.
--
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:[~2011-11-30 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 20:50 Jim Schneider [this message]
2011-12-01 1:47 ` marco atzeri
2011-12-01 9:25 ` Corinna Vinschen
2011-12-01 15:47 ` Christopher Faylor
2011-12-01 18:39 Jim Schneider
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=609C4401F424CD42A1FB3F9E26889B3E03E30E39E6@df-ex03.us.dataflux.com \
--to=jim.schneider@dataflux.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).