X-Spam-Check-By: sourceware.org
Message-ID: <43A1D735.79868CCE@dessent.net>
Date: Thu, 15 Dec 2005 12:51:01 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Vorbisfile and gdb
References: <md5:83F6DEF581D8F51F4DF729CBA0C7DF6C>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

"William J. Leslie" wrote:

> It seems that the mere presence of any symbol from vorbisfile, anywhere in the program, causes gdb to hang at the beginning of the program.  Does anyone else's gdb have the same behaviour?

I can't reproduce the hang, using the same commands:

$ ./blah
ov_open is 0x004010a0

$ gdb --quiet ./blah
(gdb) b mainCRTStartup
Breakpoint 1 at 0x401006: file ../../../../src/winsup/cygwin/crt0.c,
line 32.
(gdb) r
Starting program: /tmp/vorbisfile_bug/blah.exe 

Breakpoint 1, mainCRTStartup () at
../../../../src/winsup/cygwin/crt0.c:32
32        asm volatile ("andl $-16,%%esp" ::: "%esp");
(gdb) c
Continuing.
ov_open is 0x004010a0

Program exited normally.
(gdb) 

The first thing that came to mind when you mentioned this was that you
had a mingw/native version of the vorbis library in your search path
somewhere and that you'd somehow linked it in instead of the cygwin
one.  Doing that will cause all sorts of problems.  What does "cygcheck
blah" report?

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/