"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/
