Bug#510459: gdb back trace

[Kingsley G. Morse Jr.]

I seem to have obtained a modest back trace when
ogg123 encountered a segmentation fault.

It is

    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread 0xb79da6d0 (LWP 6358)]
    0xb7d25aae in realloc () from /lib/i686/cmov/libc.so.6
    (gdb) bt
    #0  0xb7d25aae in realloc () from /lib/i686/cmov/libc.so.6
    #1  0xb7f17314 in ?? () from /usr/lib/libao.so.2
    #2  0x00000003 in ?? ()
    #3  0x0000b130 in ?? ()
    #4  0x080571f8 in ?? ()
    #5  0x09f718b0 in ?? ()
    #6  0x080578a0 in ?? ()
    #7  0x09f76c3c in ?? ()
    #8  0xbfa7c988 in ?? ()
    #9  0xb7f17355 in ao_play () from /usr/lib/libao.so.2
    Backtrace stopped: frame did not save the PC

/lib/i686/cmov/libc.so.6 is from version 2.7-18 of libc6-i686, and
/usr/lib/libao.so.2 is from version 0.8.8-4 of
libao2.

For what it's worth, this bug seems to me to
resemble the one reported at

    https://bugs.launchpad.net/ubuntu/+source/vorbis-tools/+bug/213180

Thanks,
Kingsley