public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/55358] Valgrind errors
Date: Wed, 28 Nov 2012 19:59:00 -0000	[thread overview]
Message-ID: <bug-55358-4-Jp1t7HTkpn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55358-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #10 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-11-28 19:58:43 UTC ---
iterative_hash_canonical_type (type=0x5941dc8, val=0) at
/home/markus/gcc/gcc/gimple.c:3170
3170      *slot = (void *) mp;
(gdb) bt
#0  iterative_hash_canonical_type (type=0x5941dc8, val=0) at
/home/markus/gcc/gcc/gimple.c:3170
#1  0x0000000000d616c1 in htab_find_slot (htab=0x4030850, element=0x5941dc8,
insert=INSERT) at /home/markus/gcc/libiberty/hashtab.c:712
#2  0x000000000068ac99 in gimple_register_canonical_type (t=0x5941dc8) at
/home/markus/gcc/gcc/gimple.c:3438
#3  0x00000000004d09dc in uniquify_nodes (from=3148, data_in=0x5601990) at
/home/markus/gcc/gcc/lto/lto.c:2050
#4  lto_read_decls (resolutions=..., data=0x5d33480, decl_data=0x404a000) at
/home/markus/gcc/gcc/lto/lto.c:2089
#5  lto_file_finalize (file=<optimized out>, file_data=0x404a000) at
/home/markus/gcc/gcc/lto/lto.c:2341
#6  lto_create_files_from_ids (count=0x7fefffd98, file_data=0x404a000,
file=0x5330490) at /home/markus/gcc/gcc/lto/lto.c:2351
#7  lto_file_read (file=<optimized out>,
resolution_file=resolution_file@entry=0x5300020, count=count@entry=0x7fefffd98)
at /home/markus/gcc/gcc/lto/lto.c:2391
#8  0x00000000004d268b in read_cgraph_and_symbols (fnames=<optimized out>,
nfiles=1) at /home/markus/gcc/gcc/lto/lto.c:2966
#9  lto_main () at /home/markus/gcc/gcc/lto/lto.c:3370
#10 0x000000000082aa46 in compile_file () at /home/markus/gcc/gcc/toplev.c:545
#11 0x000000000082c96a in do_compile () at /home/markus/gcc/gcc/toplev.c:1884
#12 toplev_main (argc=17, argv=0x521ab00) at /home/markus/gcc/gcc/toplev.c:1960
#13 0x0000000004ecd885 in __libc_start_main (main=0xd0af50 <main(int, char**)>,
argc=17, ubp_av=0x7feffff18, init=<optimized out>, fini=<optimized out>, 
    rtld_fini=<optimized out>, stack_end=0x7feffff08) at libc-start.c:258
#14 0x00000000004b07e9 in _start () at ../sysdeps/x86_64/start.S:123
(gdb) p *slot
$1 = (void *) 0xa5a5a5a5a5a5a5a5
(gdb) p *mp
$2 = {base = {from = 0x5941dc8}, to = 2655783743}
(gdb) p slot
$3 = (void **) 0x4031e98
(gdb) p mp
$4 = (tree_int_map *) 0x593b620


  parent reply	other threads:[~2012-11-28 19:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 18:57 [Bug other/55358] New: " hjl.tools at gmail dot com
2012-11-21 15:31 ` [Bug other/55358] " markus at trippelsdorf dot de
2012-11-21 16:53 ` markus at trippelsdorf dot de
2012-11-21 17:17 ` markus at trippelsdorf dot de
2012-11-21 17:20 ` jakub at gcc dot gnu.org
2012-11-23 13:10 ` markus at trippelsdorf dot de
2012-11-28  8:51 ` markus at trippelsdorf dot de
2012-11-28 13:21 ` markus at trippelsdorf dot de
2012-11-28 14:48 ` jakub at gcc dot gnu.org
2012-11-28 16:50 ` jakub at gcc dot gnu.org
2012-11-28 19:59 ` markus at trippelsdorf dot de [this message]
2013-10-14  9:24 ` rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-55358-4-Jp1t7HTkpn@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).