From: "John S. Fine" Newsgroups: comp.os.msdos.djgpp Subject: Re: RSXNTDJ compile error Date: Thu, 14 May 1998 12:05:56 -0400 Organization: Erol's Internet Services Lines: 33 Message-ID: <355B1664.9B6@erols.com> References: <#sD8NWwf9GA DOT 352 AT upnetnews03> Reply-To: johnfine AT erols DOT com NNTP-Posting-Host: 207-172-240-247.s56.as4.bsd.erols.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk G Gravagne wrote: > Exception at 0x0000000001 > Application got signal at SIGSEGV > > I suspect there is a very straightforword solution to my difficulties - > perhaps I must use makelib to create a new library, and include the new > library as a link library - but as a newbie to Win32 programming, C, and Or maybe just include a library that already exists. When I asked about this problem in this newsgroup earlier, no one answered. There must be people reading this who know these answers. Blundering around in the dark, I found that when you call an entry point that isn't defined, you don't get a link time error. At run time it does a "call 0h". Since there isn't valid code at 0, you get an exception, just like you got. There must be a better way, but I stepped around in my program with the debugger until I found the bad call. It was something that should be comming from a DLL. I corrected my typo in the "-l" switch for the associated library, and that problem was fixed. There was some program (I forget the name) that I was using to dump information from the .EXE file including the very important info of what symbols it was expecting to import from which DLLs. If a DLL that you know you need is missing from that list then that is the problem. -- http://www.erols.com/johnfine/ http://www.geocities.com/SiliconValley/Peaks/8600/