public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "james.hilliard1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109256] New: Error: failed to link 'linked_maps2.bpf.o': Cannot allocate memory (12) Date: Thu, 23 Mar 2023 04:06:02 +0000 [thread overview] Message-ID: <bug-109256-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109256 Bug ID: 109256 Summary: Error: failed to link 'linked_maps2.bpf.o': Cannot allocate memory (12) Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: james.hilliard1 at gmail dot com Target Milestone: --- I'm seeing this gen object error which does not occur in llvm for a bpf test(which uses both linked_maps1.c and linked_maps2.c) in bpf-next. It seems this is triggering a double free in libbpf, not entirely clear if this is a gcc issue or libbpf issue. GCC gen object failure: ==2125110== Command: /home/buildroot/bpf-next/tools/testing/selftests/bpf/tools/sbin/bpftool --debug gen object /home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_gcc/linked_maps.linked1.o /home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_gcc/linked_maps1.bpf.o /home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_gcc/linked_maps2.bpf.o ==2125110== libbpf: linker: adding object file '/home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_gcc/linked_maps1.bpf.o'... libbpf: linker: adding object file '/home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_gcc/linked_maps2.bpf.o'... Error: failed to link '/home/buildroot/bpf-next/tools/testing/selftests/bpf/bpf_gcc/linked_maps2.bpf.o': Cannot allocate memory (12) ==2125110== Invalid free() / delete / delete[] / realloc() ==2125110== at 0x484B0C4: free (vg_replace_malloc.c:884) ==2125110== by 0x17F8AB: bpf_linker__free (linker.c:204) ==2125110== by 0x12833C: do_object (gen.c:1608) ==2125110== by 0x12CDAB: cmd_select (main.c:206) ==2125110== by 0x129B53: do_gen (gen.c:2332) ==2125110== by 0x12CDAB: cmd_select (main.c:206) ==2125110== by 0x12DB9E: main (main.c:539) ==2125110== Address 0xda4b420 is 0 bytes after a block of size 0 free'd ==2125110== at 0x484B027: free (vg_replace_malloc.c:883) ==2125110== by 0x484D6F8: realloc (vg_replace_malloc.c:1451) ==2125110== by 0x181FA3: extend_sec (linker.c:1117) ==2125110== by 0x182326: linker_append_sec_data (linker.c:1201) ==2125110== by 0x1803DC: bpf_linker__add_file (linker.c:453) ==2125110== by 0x12829E: do_object (gen.c:1593) ==2125110== by 0x12CDAB: cmd_select (main.c:206) ==2125110== by 0x129B53: do_gen (gen.c:2332) ==2125110== by 0x12CDAB: cmd_select (main.c:206) ==2125110== by 0x12DB9E: main (main.c:539) ==2125110== Block was alloc'd at ==2125110== at 0x484876A: malloc (vg_replace_malloc.c:392) ==2125110== by 0x484D6EB: realloc (vg_replace_malloc.c:1451) ==2125110== by 0x181FA3: extend_sec (linker.c:1117) ==2125110== by 0x182326: linker_append_sec_data (linker.c:1201) ==2125110== by 0x1803DC: bpf_linker__add_file (linker.c:453) ==2125110== by 0x12829E: do_object (gen.c:1593) ==2125110== by 0x12CDAB: cmd_select (main.c:206) ==2125110== by 0x129B53: do_gen (gen.c:2332) ==2125110== by 0x12CDAB: cmd_select (main.c:206) ==2125110== by 0x12DB9E: main (main.c:539)
next reply other threads:[~2023-03-23 4:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-23 4:06 james.hilliard1 at gmail dot com [this message] 2023-03-23 4:11 ` [Bug target/109256] " pinskia at gcc dot gnu.org 2023-03-23 4:21 ` james.hilliard1 at gmail dot com 2023-03-28 3:10 ` james.hilliard1 at gmail dot com 2023-03-29 0:13 ` 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-109256-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: 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).