From: Rod DOT Bates AT wichita DOT boeing DOT com (Bates, Rod)
Subject: bad value at __imp_dll_crt0_FP11per_process
9 Oct 1998 07:13:42 -0700
Message-ID: <6C7E2A10BB01D111929500400B406DDEE63939.cygnus.gnu-win32@xch-wch-02.ks.boeing.com>
Mime-Version: 1.0
Content-Type: text/plain
To: "'gnu-win32 AT cygnus DOT com'" <gnu-win32 AT cygnus DOT com>

Can anyone help explain this.  

I built an executable using gcc.  It gets a segmentation
fault right away.  It calls _cygwin_crt0, which calls
_dll_crt0_FP11per_process.  This jumps to the contents
of a word which has the bad address.  gdb x/x on this
word reports <__imp_dll_crt0_FP11per_process>: 0x371ab0,
which is the value listed in the segmentation fault. 

There is no _imp_dll_crt0_FP11per_process in the
objdump -S listing.  nm lists this symbol with '?' and
address of the indirect work. 

Did I fail to get something linked in properly?
To have the right path for .dll's? 

An identical build (except for changes to my application
code, which this isn't getting to) has worked as expected
in the past.  
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".