public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wbx at openadk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98784] [11/12/13/14 Regression] problematic build of uClibc with -fPIC
Date: Tue, 08 Aug 2023 09:51:43 +0000	[thread overview]
Message-ID: <bug-98784-4-LGQm0M6SYK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98784-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98784

Waldemar Brodkorb <wbx at openadk dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wbx at openadk dot org

--- Comment #18 from Waldemar Brodkorb <wbx at openadk dot org> ---
Hi,

still happens with gcc 13.2.0.
You can boot a shell and then in strace you see a segfault error:

[pid    28] fstat64(3, {st_mode=S_IFDIR|S_ISVTX|0777, st_size=400, ...}) = 0
[pid    28] brk(0x154000)               = 0x154000
[pid    28] getdents64(3, 0xefb11b80 /* 20 entries */, 4096) = 496
[pid    28] brk(0x155000)               = 0x155000
[pid    28] lstat64("./init", {st_mode=S_IFLNK|0777, st_size=10, ...}) = 0
[pid    28] lstat64("./var", {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
[pid    28] lstat64("./usr", {st_mode=S_IFDIR|0755, st_size=120, ...}) = 0
[pid    28] lstat64("./tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=40, ...}) =
0
[pid    28] lstat64("./sys", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
[pid    28] lstat64("./sbin", {st_mode=S_IFDIR|0755, st_size=1420, ...}) = 0
[pid    28] lstat64("./run", {st_mode=S_IFDIR|0777, st_size=40, ...}) = 0
[pid    28] lstat64("./root", {st_mode=S_IFDIR|0755, st_size=60, ...}) = 0
[pid    28] lstat64("./proc", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
[pid    28] lstat64("./mnt", {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
[pid    28] lstat64("./media", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=40, ...})
= 0
[pid    28] lstat64("./linuxrc", {st_mode=S_IFLNK|0777, st_size=11, ...}) = 0
[pid    28] lstat64("./lib", {st_mode=S_IFDIR|0755, st_size=260, ...}) = 0
[pid    28] lstat64("./etc", {st_mode=S_IFDIR|0755, st_size=640, ...}) = 0
[pid    28] lstat64("./dev", {st_mode=S_IFDIR|0755, st_size=640, ...}) = 0
[pid    28] lstat64("./boot", {st_mode=S_IFDIR|0755, st_size=40, ...}) = 0
[pid    28] lstat64("./bin", {st_mode=S_IFDIR|0755, st_size=1920, ...}) = 0
[pid    28] getdents64(3, 0xefb11b80 /* 0 entries */, 4096) = 0
[pid    28] close(3)                    = 0
[pid    28] write(1, "\33[1;34mbin\33[m      \33[1;34metc\33[m"..., 109bin     
etc      linuxrc  proc     sbin     usr
) = 109
[pid    28] write(1, "\33[1;34mboot\33[m     \33[1;36minit\33["..., 109boot    
init     media    root     sys      var
) = 109
[pid    28] write(1, "\33[1;34mdev\33[m      \33[1;34mlib\33[m"..., 90dev     
lib      mnt      run      tmp
) = 90
[pid    28] exit_group(0)               = ?
[pid    28] +++ exited with 0 +++
<... rt_sigsuspend resumed>)            = ? ERESTARTNOHAND (To be restarted if
no handler)
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=28, si_uid=0,
si_status=0, si_utime=0, si_stime=3 /* 0.03 s */} ---
getrusage(RUSAGE_CHILDREN, {ru_utime={tv_sec=0, tv_usec=0}, ru_stime={tv_sec=0,
tv_usec=0}, ...}) = 0
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG|WSTOPPED|WCONTINUED,
NULL) = 28
getrusage(RUSAGE_CHILDREN, {ru_utime={tv_sec=0, tv_usec=8000},
ru_stime={tv_sec=0, tv_usec=32000}, ...}) = 0
wait4(-1, 0xefbe678c, WNOHANG|WSTOPPED|WCONTINUED, NULL) = -1 ECHILD (No child
processes)
sigreturn({mask=[INT RT_1 RT_8 RT_15 RT_21 RT_23 RT_31]}) = -1 (errno 629)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=NULL} ---
+++ killed by SIGSEGV +++

Any tipps how to debug this?

best regards
 Waldemar

  parent reply	other threads:[~2023-08-08  9:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 22:13 [Bug c/98784] New: [gcc 8.4/9.3/10] sparcv8 regression romain.naour at gmail dot com
2021-01-21 23:01 ` [Bug c/98784] " ebotcazou at gcc dot gnu.org
2021-01-21 23:26 ` romain.naour at gmail dot com
2021-01-21 23:43 ` ebotcazou at gcc dot gnu.org
2021-01-22  7:33 ` [Bug target/98784] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org
2021-01-23 11:43 ` romain.naour at gmail dot com
2021-01-23 17:33 ` ebotcazou at gcc dot gnu.org
2021-01-23 20:07 ` romain.naour at gmail dot com
2021-01-23 21:56 ` [Bug target/98784] [8/9/10/11 Regression] problematic build of uClibc with -fPIC ebotcazou at gcc dot gnu.org
2021-01-24  9:17 ` ebotcazou at gcc dot gnu.org
2021-01-26 21:24 ` romain.naour at gmail dot com
2021-01-26 22:29 ` romain.naour at gmail dot com
2021-04-09  8:08 ` rguenth at gcc dot gnu.org
2021-05-14  9:54 ` [Bug target/98784] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:19 ` rguenth at gcc dot gnu.org
2021-06-28 16:40 ` yann at sionneau dot net
2021-06-28 16:50 ` yann at sionneau dot net
2022-05-27  9:44 ` [Bug target/98784] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-07-07 10:38 ` [Bug target/98784] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-08-08  9:51 ` wbx at openadk dot org [this message]
2024-04-30 15:05 ` [Bug target/98784] [11/12/13/14/15 " dm.chestnykh at gmail dot com
2024-04-30 17:55 ` dm.chestnykh at gmail dot com
2024-04-30 17:59 ` pinskia 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-98784-4-LGQm0M6SYK@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).