Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<3DBA4AC2.94D2831F@citech.com.ph>
Date:	Sat, 26 Oct 2002 15:56:50 +0800
From:	Rommel Garcia Custodio <rommel AT citech DOT com DOT ph>
Organization:	Canon Information Technologies Philippines Inc
X-Accept-Language:	en,ja
MIME-Version:	1.0
To:	cygwin <cygwin AT cygwin DOT com>
Subject:	[CYGWIN] SIGSEGV while debugging app when compiled by latest gcc

good morning,

   short intro, ive been using cygwin for approx 3 years now.
  and this is the first time this happened to me.

   im building an application under cygwin. needless to say
  my application ran properly when compiled by older versions
  of the gcc compiler.

   whenever i run my application under gdb i get a segmentation
  violation when i run my application.

   heres a backtrace:

$ gdb -nw tst.exe
GNU gdb 5.0 (20010428-3)
Copyright 2001 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) r
Starting program:
/home/rommel/devel_v3/CLEANROOM/v3.02/v3.02.01.01/red/cbtps3_b
qb/testsuite/tester/tst.exe

Program received signal SIGSEGV, Segmentation fault.
0x77e88207 in _libwinmm_a_iname ()
(gdb) bt
#0  0x77e88207 in _libwinmm_a_iname ()
#1  0x0044b5c0 in cygwin_premain2 ()
#2  0x61083a7d in _libwinmm_a_iname ()
#3  0x61083ae6 in _libwinmm_a_iname ()
#4  0x61083b30 in _libwinmm_a_iname ()
#5  0x61082989 in _libwinmm_a_iname ()
#6  0x610852c5 in _libwinmm_a_iname ()
#7  0x61085409 in _libwinmm_a_iname ()
#8  0x00449e20 in __register_frame_info_bases ()
#9  0x00449e68 in __register_frame_info ()
#10 0x0040105f in __do_frame_init ()
#11 0x61005ed5 in _libwinmm_a_iname ()
#12 0x61007a1b in _libwinmm_a_iname ()
#13 0x004040fa in main (argc=1, argv=0x10042d38) at tst_main.c:480
#14 0x61007549 in _libwinmm_a_iname ()
#15 0x6100780d in _libwinmm_a_iname ()
#16 0x0044b1b2 in cygwin_crt0 ()
#17 0x0040103c in mainCRTStartup ()
#18 0x77e9ca90 in _libwinmm_a_iname ()
(gdb)

   im compiling my application using:

$ gcc -v
Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/specs
Configured with: /netrel/src/gcc-3.2-1/configure
--enable-languages=c,c++,f77,ja
va --enable-libgcj --enable-threads=posix --with-system-zlib
--enable-nls --with
out-included-gettext --enable-interpreter --disable-sjlj-exceptions
--disable-ve
rsion-specific-runtime-libs --enable-shared --build=i686-pc-linux
--host=i686-pc
-cygwin --target=i686-pc-cygwin --enable-haifa --prefix=/usr
--exec-prefix=/usr
--sysconfdir=/etc --libdir=/usr/lib --includedir=/nonexistent/include
--libexecd
ir=/usr/sbin
Thread model: posix
gcc version 3.2 20020818 (prerelease)

   i suspected that there could be incompatibilities b/n gcc and gdb.
  when i debug my app with gdb this problem occurs though it doesnt
  occur when i run my app on top of Win2k.

   im currently stumped!

regards, mela.
-- 
rommel garcia custodio                 ci-tech Bluetooth (tm) QA Team

wasurenai Melody... kuchizusamu kokoro de...
ima yori mo motto kimi ga wakaru made... No Never The End

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -