public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/51297] [4.7 regressions] Many gcov tests FAIL on Tru64 UNIX, Solaris 8 Date: Thu, 24 Nov 2011 18:41:00 -0000 [thread overview] Message-ID: <bug-51297-4-ttM2iDV6lk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51297-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51297 --- Comment #1 from Nathan Sidwell <nathan at gcc dot gnu.org> 2011-11-24 18:30:40 UTC --- The line numbers in the backtrace don't seem to correspond to current sources. for instance line 866 is the definition of find_source, not the location of one of the two bsearch calls. which of the two bsearch calls is blowing up? this one: name_map = (name_map_t *)bsearch (file_name, names, n_names, sizeof (*names), name_search); or this one: name_map = (name_map_t *)bsearch (canon, names, n_names, sizeof (*names), name_search); What are the values being passed to the bsearch call? Oh, I see that it appears the string being passed to 'find_source' is unreadable: #2 0x08056d88 in find_source (file_name=0x80a2f70 <error reading variable>) at /vol/gcc/src/hg/trunk/local/gcc/gcov.c:866 What does gcov-dump -lo tell you about the gcno file?
next prev parent reply other threads:[~2011-11-24 18:31 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-24 18:38 [Bug gcov-profile/51297] New: " ro at gcc dot gnu.org 2011-11-24 18:41 ` nathan at gcc dot gnu.org [this message] 2011-11-24 18:54 ` [Bug gcov-profile/51297] [4.7 regression] Many gcov tests FAIL on Tru64, Solaris 8 and 9 ebotcazou at gcc dot gnu.org 2011-11-24 19:25 ` ebotcazou at gcc dot gnu.org 2011-11-24 19:34 ` nathan at gcc dot gnu.org 2011-11-24 20:52 ` ebotcazou at gcc dot gnu.org 2011-11-24 22:12 ` nathan at acm dot org 2011-11-24 22:13 ` ebotcazou at gcc dot gnu.org 2011-11-24 23:15 ` nathan at acm dot org 2011-11-25 1:02 ` ebotcazou at gcc dot gnu.org 2011-11-25 10:44 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-11-26 23:11 ` nathan at gcc dot gnu.org 2011-11-27 3:03 ` nathan at gcc dot gnu.org 2011-12-06 14:11 ` 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-51297-4-ttM2iDV6lk@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: linkBe 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).