Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	zehavi AT il DOT ibm DOT com
X-Lotus-FromDomain:	IBMIL AT IBMDE
To:	cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<C1256863.003C4AFF.00@d12mta02.de.ibm.com>
Date:	Tue, 11 Jan 2000 12:58:30 +0200
Subject:	Re: GDB: Program received signal SIGSEGV, Segmentation fault.
	0x77f6cde6 in ?? ()
Mime-Version:	1.0

Hi,
Here is some additional information about the problem.
I also brought djgcc and djgdb package and got the following results.
1. When I run Cygnus gdb with any program compiled with Cygnus GCC I get the
crash
2.  When I run Cygnus gdb on a program compiled with djgcc I get "File is in
invalid format" and gdb fails to load it
3. When I run djgdb with a program compiled with djgcc it runs fine
4. When I run djgdb with program compiled with Cygnus GCC I get "File is in
invalid format"
5. Cygnus gdb did not fail on some programs not compile with Cygnus GCC or djgcc
for example ghostscript worked under Cygnus gdb.

All programs run fine not under gdb
I rechecked my path and I only have one cygwin1.dll and also simplified it as
much as possible (left only Cygnus). This did not solve the problem.

Avi.
---------------------- Forwarded by Abraham Zehavi/Haifa/IBM on 01/11/2000 12:50
PM ---------------------------

Abraham Zehavi
01/05/2000 12:37 PM

To:   cygwin AT sourceware DOT cygnus DOT com
cc:
From: Abraham Zehavi/Haifa/IBM AT IBMIL
Subject:  GDB: Program received signal SIGSEGV, Segmentation fault. 0x77f6cde6
      in ?? ()


I have tried to run the Cygnus package version b20.1 on Windows NT 4.
Any program that I run under gdb crashes with the above message.
Also it reports a lot of system DLLs not having debug information (they are not
supposed to have).
Here is the output after entering the run command from "gdb ls.exe"

[failed reading symbols from DLL]
"/WINNT/system32/GDI32.dll": error reading line numbers

(no debugging symbols found)...77e10000:/WINNT/system32/RPCRT4.dll

[failed reading symbols from DLL]
"/WINNT/System32/lpk.dll": error reading line numbers


[failed reading symbols from DLL]
"/WINNT/System32/lpkbidi.dll": error reading line numbers


(no debugging symbols found)...67f60000:/WINNT/System32/NFPROC.DLL

Program received signal SIGSEGV, Segmentation fault.
0x77f6cde6 in ?? ()

HELP any ideas please send me a response directly.
Avi.




--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -