This is the mail archive of the
mailing list for the Cygwin project.
Re: perl fork error: child_info_fork::abort: data segment start: - example code!
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 8 Feb 2012 15:27:12 +0100
- Subject: Re: perl fork error: child_info_fork::abort: data segment start: - example code!
- References: <loom.20120208T143015email@example.com>
On Feb 8 13:59, Heiko Elger wrote:
> We use Symantec Endpoint Protection 12.1.x!
> Yes - I know it is a BLODA - but please go on reading - my company want to
> contact Symantec cause of these ERRORs.
> The following simple perl script will produce the following error:
> ***** snip snip snip ***
> ********* snip snip snip ****************
> Symantec is installed and is running but it is complete deactivated with
> context menu.
> What does this error mean - please a little bit in delail?
> 0 [main] perl 8916 child_info_fork::abort: data segment start: parent
> (0xC1A000) != child(0xA6A000)
The code checks if the data and bss segments of a given DLL, which was
already loaded by the parent process, is in the same spot in the child
process. If not, the DLL has been loaded into another address in the
child, which will likely result in a nonfunctional forked process.
> So why I will get this error - only cause of symantec?
Perhaps. Probably. I'm not sure. However, the above addresses
0xC1A000 and 0xA6A000 are *very* unlikely DLL load addresses in a
Windows system. Usually DLLs are loaded at addresses beyond
0x10000000, preferredly to the address stored in the DLL header.
As I said , I don't no if SEP is really the culprit here, but at
least the address are weird. And...
> If uninstalling SEP all works fine.
...that's kind of a clue.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple