public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/97594] [11 Regression] new test case gcc.dg/tree-prof/pr97461.c execution failure
Date: Tue, 27 Oct 2020 15:43:25 +0000 [thread overview]
Message-ID: <bug-97594-4-9vnbXnoXIF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97594-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97594
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #1)
> Mine, I see a strange error:
>
> $ Program received signal SIGBUS, Bus error.
> 0x00003fffb7ceddbc in __GI__IO_link_in () from /lib64/libc.so.6
> Missing separate debuginfos, use: debuginfo-install
> glibc-2.17-307.el7.1.ppc64le
> (gdb) bt
> #0 0x00003fffb7ceddbc in __GI__IO_link_in () from /lib64/libc.so.6
> #1 0x00003fffb7cebe58 in _IO_new_file_init_internal () from /lib64/libc.so.6
> #2 0x00003fffb7cd9dcc in fdopen@@GLIBC_2.17 () from /lib64/libc.so.6
> #3 0x0000000010002928 in __gcov_open (name=0x100204f0 <memory+8>
> "/home/marxin/Programming/gcc/objdir/gcc/testsuite/gcc35/pr97461.gcda") at
> ../../../libgcc/../gcc/gcov-io.c:171
> #4 0x0000000010002db8 in gcov_exit_open_gcda_file (gi_ptr=0x10020408,
> gi_ptr=0x10020408, gf=<synthetic pointer>) at
> ../../../libgcc/libgcov-driver-system.c:312
> #5 dump_one_gcov (run_max=<optimized out>, run_counted=<optimized out>,
> gf=<synthetic pointer>, gi_ptr=0x10020408) at
> ../../../libgcc/libgcov-driver.c:478
> #6 gcov_do_dump (list=<optimized out>, run_counted=<optimized out>) at
> ../../../libgcc/libgcov-driver.c:555
> #7 0x00000000100047d8 in __gcov_dump_one (root=0x10040590 <__gcov_root>) at
> ../../../libgcc/libgcov-driver.c:578
> #8 __gcov_dump_one (root=0x10040590 <__gcov_root>) at
> ../../../libgcc/libgcov-driver.c:573
> #9 __gcov_exit () at ../../../libgcc/libgcov-driver.c:600
> #10 0x0000000010000e18 in _sub_D_00100_1 ()
> #11 0x00003fffb7fc7c68 in _dl_fini () from /lib64/ld64.so.2
> #12 0x00003fffb7ca4a34 in __run_exit_handlers () from /lib64/libc.so.6
> #13 0x00003fffb7ca4a84 in exit () from /lib64/libc.so.6
> #14 0x00003fffb7c85308 in generic_start_main.isra.0 () from /lib64/libc.so.6
> #15 0x00003fffb7c854f4 in __libc_start_main () from /lib64/libc.so.6
> #16 0x0000000000000000 in ?? ()
All right, so the test-case overloads malloc and returns a memory that is a
static buffer. For some reason, it leads to SEGBUS.
Do Power people know what's causing that?
next prev parent reply other threads:[~2020-10-27 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 14:48 [Bug other/97594] New: " seurer at gcc dot gnu.org
2020-10-27 15:09 ` [Bug gcov-profile/97594] [11 Regression] " rguenth at gcc dot gnu.org
2020-10-27 15:11 ` marxin at gcc dot gnu.org
2020-10-27 15:43 ` marxin at gcc dot gnu.org [this message]
2020-11-06 6:10 ` linkw at gcc dot gnu.org
2020-11-06 13:18 ` marxin at gcc dot gnu.org
2020-11-06 13:49 ` marxin 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-97594-4-9vnbXnoXIF@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).