On 9/30/2011 12:04 PM, Marc Girod wrote:
Hello,
I keep my installation up-to-date on a weekly basis, and never fail to
rebaseall/peflagsall as many times as needed to be able to start emacs
in an X session without fork errors. Then I do a perlrebase.
However, I eventually get STATUS_ACCESS_VIOLATION errors, in
various contexts, e.g. (last now) doing a dired.
I have been keeping the *stackdump files produced, and even logging
their contents for fear they would get overwritten.
I note that the value of eip (instruction pointer register?) reported is
often the same. Here are the data for the last event:
[cut]
2 [main] emacs 6660 child_copy: linked dll data write copy failed,
0x26B000..0x274C8C, done 0, windows pid 6692, Win32 error 487
And I checked:
~> net helpmsg 487
Attempt to access invalid address.
My understanding, from reading previous threads in the list, is that
some Windows process performs DLL injection, which modifies the
memory map of the emacs process, so that it doesn't match the
expectation of 'ls' while being forked as part of executing 'dired'.
Is there any way to identify this Windows process, or the exact DLL,
so as to know in advance how to rebase the processes to avoid this
conflict? Can I use the above data for that purpose?
Or is it doomed?
And is my understanding flawed?
Thanks,
Marc
Problem reports: http://cygwin.com/problems.html
so at least we have an idea of your system
in addition, have you checked
http://cygwin.com/faq/faq.using.html#faq.using.bloda
Antivirus and driver are the most likely culprits.
Regards
Marco
--
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
