public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/61078] New: ESA mode bootstrap failure since r209897
Date: Tue, 06 May 2014 13:30:00 -0000	[thread overview]
Message-ID: <bug-61078-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 61078
           Summary: ESA mode bootstrap failure since r209897
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: krebbel at gcc dot gnu.org

Regression hunt indicates that r209897 might have caused a bootstrap failure on
s390 ESA mode:

Bootstrap dies reproducable with a segfault in bash:
...
make install-leaf DESTDIR=../.././gcc \
  slibdir= libsubdir= MULTIOSDIR=.
make[4]: Entering directory
`/build/patched/gcc-4.10.0-build/s390-ibm-linux-gnu/libgcc'
/bin/sh /build/patched/gcc/libgcc/../mkinstalldirs ../.././gcc
/usr/bin/install -c -m 644 libgcc_eh.a ../.././gcc/
chmod 644 ../.././gcc/libgcc_eh.a
ranlib ../.././gcc/libgcc_eh.a
/bin/sh /build/patched/gcc/libgcc/../mkinstalldirs ../.././gcc;
/usr/bin/install -c -m 644 ./libgcc_s.so.1 ../.././gcc/libgcc_s.so.1; rm -f
../.././gcc/libgcc_s.so; ln -s libgcc_s.so.1 ../.././gcc/libgcc_s.so
/bin/sh /build/patched/gcc/libgcc/../mkinstalldirs ../.././gcc
make[4]: *** [install-leaf] Segmentation fault
make[4]: Leaving directory
`/build/patched/gcc-4.10.0-build/s390-ibm-linux-gnu/libgcc'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/build/patched/gcc-4.10.0-build/s390-ibm-linux-gnu/libgcc'
make[2]: *** [all-stage2-target-libgcc] Error 2
make[2]: Leaving directory `/build/patched/gcc-4.10.0-build'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory `/build/patched/gcc-4.10.0-build'
make: *** [all] Error 2


[pid  1082] vfork(Process 1088 attached
 <unfinished ...>
[pid  1088] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
[pid  1088] prlimit64(0, RLIMIT_STACK, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}, NULL) = 0
[pid  1088] execve("/bin/sh", ["/bin/sh", "-c", "subdirs='testsuite';
\\\ntarget=`e"...], [/* 172 vars */] <unfinished ...>
[pid  1082] <... vfork resumed> )       = 1088
[pid  1082] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
[pid  1082] wait4(-1,  <unfinished ...>
[pid  1088] <... execve resumed> )      = 0
....
[pid  1088] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
si_errno=1825521056, si_addr=0} ---
[pid  1088] +++ killed by SIGSEGV +++
[pid  1082] <... wait4 resumed> [{WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV}],
0, NULL) = 1088
[pid  1082] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=1088,
si_status=SIGSEGV, si_utime
=0, si_stime=0} ---
[pid  1082] sigreturn() (mask [])       = 1088

I've verified that reverting the patch "fixes" the problem. I haven't figured
out yet how the patch is related to the problem. Perhaps the execve arguments
for /bin/sh somehow get messed up with the patch?!


             reply	other threads:[~2014-05-06 13:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 13:30 krebbel at gcc dot gnu.org [this message]
2014-05-06 13:40 ` [Bug bootstrap/61078] [4.10 Regression] " rguenth at gcc dot gnu.org
2014-08-25 10:48 ` [Bug bootstrap/61078] [5 " krebbel at gcc dot gnu.org
2014-08-25 10:56 ` krebbel at gcc dot gnu.org
2014-08-28 15:15 ` krebbel at gcc dot gnu.org
2014-08-28 15:17 ` krebbel at gcc dot gnu.org
2014-08-28 16:00 ` jgreenhalgh at gcc dot gnu.org
2014-08-29 18:13 ` krebbel at gcc dot gnu.org
2014-09-03  8:06 ` krebbel at gcc dot gnu.org
2014-09-03  8:18 ` krebbel 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-61078-4@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).