public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "liaozhicai at cigtech dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/31732] New: ld.so is trapped in __libc_csu_init function, no return or forward when load a normal ELF process Date: Mon, 13 May 2024 03:06:54 +0000 [thread overview] Message-ID: <bug-31732-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31732 Bug ID: 31732 Summary: ld.so is trapped in __libc_csu_init function, no return or forward when load a normal ELF process Product: glibc Version: 2.30 Status: UNCONFIRMED Severity: normal Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: liaozhicai at cigtech dot com Target Milestone: --- context: OS:Linux saturn2-sfu-eng 4.14.172.saturn2-sfu-r2.2.1.3 #1 Sat May 11 08:47:16 UTC 2024 mips GNU/Linux arch:mips 32 we employ kernel API fork/execv and try to load a ELF-format file with a file name of MecMgr, as a result the main function is not entered occationally. tracking the routine, it is found that the process is trapped in __libc_csu_init function, no return or forward, and if add some printf-clauses in the function showing us where is is when error occurred, the issue cann't be reproduced again. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-05-13 3:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-13 3:06 liaozhicai at cigtech dot com [this message] 2024-05-14 9:58 ` [Bug dynamic-link/31732] " fweimer at redhat dot com 2024-05-16 3:12 ` liaozhicai at cigtech dot com 2024-05-16 11:47 ` fweimer at redhat dot com 2024-05-17 2:34 ` liaozhicai at cigtech dot com 2024-05-17 8:55 ` fweimer at redhat dot com 2024-06-26 8:09 ` liaozhicai at cigtech dot com 2024-06-26 8:12 ` fweimer at redhat dot com 2024-06-27 2:05 ` liaozhicai at cigtech dot com 2024-06-27 2:22 ` liaozhicai at cigtech dot com
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-31732-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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).