[Bug target/12588] [3.4 Regression] ICE in function_value
mckelvey at maskull dot com
gcc-bugzilla@gcc.gnu.org
Sat Oct 25 02:46:00 GMT 2003
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12588
------- Additional Comments From mckelvey at maskull dot com 2003-10-25 02:41 -------
Subject: Re: [3.4 Regression] ICE in function_value
On Wednesday 22 October 2003 15:42 pm, pinskia 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=12588
>
>
> pinskia at gcc dot gnu dot org changed:
>
> What |Removed |Added
> ---------------------------------------------------------------------------
>- Status|NEW |WAITING
>
>
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2003-10-22
> 22:42 ------- Most likely fixed by:
> <http://gcc.gnu.org/ml/gcc-patches/2003-10/msg01970.html>. Can you try
> bootstrapping again?
Yes, it no longer ICEs. But this code seg faults:
#include <iostream>
int
main(int, char **)
{
return 0;
}
Results from gdb 5.3:
warning: Hit heuristic-fence-post without finding
warning: enclosing function for address 0xa09f000000200
This warning occurs if you are debugging a function without any symbols
(for example, in a stripped executable). In that case, you may wish to
increase the size of the search with the `set heuristic-fence-post' command.
Otherwise, you told GDB there was a function where there isn't one, or
(more likely) you have encountered a bug in GDB.
warning: Hit heuristic-fence-post without finding
warning: enclosing function for address 0xa09f000000200
#0 0x000a09f000000200 in ?? ()
(gdb) bt
#0 0x000a09f000000200 in ?? ()
#1 0x0000020000099d10 in _Impl (this=0x2000013ff80, __refs=2199024562468)
at ../../../../gcc/libstdc++-v3/src/locale_init.cc:256
#2 0x0000020000099d10 in _Impl (this=Cannot access memory at address 0x18
)
at ../../../../gcc/libstdc++-v3/src/locale_init.cc:256
Cannot access memory at address 0x40
(gdb)
More information about the Gcc-bugs
mailing list