[Bug target/12471] no backtrace into libstdc++ possible

["mxu at cae dot wisc dot edu" <gcc-bugzilla at gcc dot gnu dot org>]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12471



------- Additional Comments From mxu at cae dot wisc dot edu  2003-10-03 14:27 -------
Subject: Re:  no backtrace into libstdc++ possible

ebotcazou,

Thanks for investigate. You mean gdb 6.x will fix it? I though
gdb and dbx don't compatible, you mean I can use dbx to debug
gcc compiled program?

Thanks,

-Min

On Fri, 03 Oct 2003 ebotcazou at gcc dot gnu dot org wrote :
> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12471
> 
> 
> ebotcazou at gcc dot gnu dot org changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|ASSIGNED                    |RESOLVED
>          Resolution|                            |INVALID
> 
> 
> ------- Additional Comments From ebotcazou at gcc dot gnu dot org  2003-10-03 06:47 -------
> This is a GDB 5.x bug (see PR 1044 in the GDB bug database). Here's the session
> with dbx:
> 
> (dbx) where
> =>[1] _libc_write(0x1, 0xff240f9c, 0x400, 0xff23e164, 0xff20f014, 0xff383280),
> at 0xff21d238
>   [2] _xflsbuf(0xff23e174, 0xff24139c, 0xff23dce8, 0xff23e164, 0xff20f014,
> 0xff00), at 0xff20f128
>   [3] _flsbuf(0x61, 0xff23e174, 0x61, 0x4, 0x0, 0xff3d6a18), at 0xff20c658
>   [4] _fwrite_unlocked(0xffbff99f, 0x1, 0x1, 0xff23e174, 0x0, 0xff3836f8), at
> 0xff2108fc
>   [5] fwrite(0xffbff99f, 0x1, 0x1, 0xff23e174, 0x0, 0xff333f3c), at 0xff210430
>   [6]
> _ZNSt13basic_filebufIcSt11char_traitsIcEE22_M_convert_to_externalEPciRiS4_(0xff383938,
> 0xffbff99f, 0x1, 0xffbff9a4, 0xffbff9a0, 0x10), at 0xff3379e8
>   [7]
> _ZNSt13basic_filebufIcSt11char_traitsIcEE18_M_really_overflowEi(0xffffffff, 0x1,
> 0x0, 0x0, 0x0, 0x0), at 0xff3377a8
>   [8] _ZNSt13basic_filebufIcSt11char_traitsIcEE8overflowEi(0xff383938, 0x61,
> 0x0, 0x1002, 0xff383938, 0xff383280), at 0xff3376b8
>   [9] _ZNSt15basic_streambufIcSt11char_traitsIcEE6xsputnEPKci(0x0, 0x10ce9, 0x1,
> 0x1002, 0x20fa0, 0xff383280), at 0xff357460
>   [10] _ZNSo5writeEPKci(0x20fa0, 0x10ce8, 0x1, 0x7efefeff, 0x81010100, 0xff00),
> at 0xff352340
>   [11] _ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_PKc(0x1, 0x10ce8,
> 0xff3846d4, 0x4, 0x0, 0xff3d6a18), at 0xff352ac8
>   [12] main(0x1, 0xffbffc6c, 0xffbffc74, 0x20f98, 0x0, 0x0), at 0x10b5c
> 
> 
> 
> 
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.