From: Philippe Gerum <rpm@xenomai.org>
To: Junxiao Chang <junxiao.chang@intel.com>
Cc: xenomai@lists.linux.dev, yuan1.wang@intel.com
Subject: Re: [PATCH libevl 2/2] tests: ptrace-sync: only integrate ptrace-sync in debug build
Date: Fri, 23 Jan 2026 14:28:06 +0100 [thread overview]
Message-ID: <87ecng1ms9.fsf@xenomai.org> (raw)
In-Reply-To: <20260124114232.1186577-2-junxiao.chang@intel.com> (Junxiao Chang's message of "Sat, 24 Jan 2026 19:42:32 +0800")
Junxiao Chang <junxiao.chang@intel.com> writes:
> ptrace-sync test case needs to load debug symbol in gdb. There is
> debug symbol in debug build. If buildtype is release, this case
> should not be integrated because it doesn't have debug symbol.
>
I don't think so, -g and the optimization level are unrelated in this
day and age (have been at some point though, many, many moons ago).
This is the output log of an x86 build for ptrace-sync.c with
--buildtype release passed to meson, -O2 and -g are both set.
[111/226] x86_64-blade-linux-gcc -m64 -march=nehalem -mtune=generic -mfpmath=sse -msse4.2 -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/var/lab/sdk/cpc/x86-corei7/blade-2025.10/sysroots/corei7-64-blade-linux -Itests/ptrace-sync.p -Itests -I../../../../git/xenomai/v4/libevl/tests -Iinclude -I../../../../git/xenomai/v4/libevl/include -I../../../../git/xenomai/v4/libevl/lib/arch/x86/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -Werror -std=gnu11 -O3 -pipe -Wstrict-aliasing -Wno-unused-parameter -Wno-pedantic -D_GNU_SOURCE -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wshadow=local -Wstrict-prototypes -Wmissing-prototypes -O2 -g -pthread -g -MD -MQ tests/ptrace-sync.p/ptrace-sync.c.o -MF tests/ptrace-sync.p/ptrace-sync.c.o.d -o tests/ptrace-sync.p/ptrace-sync.c.o -c ../../../../git/xenomai/v4/libevl/tests/ptrace-sync.c
~# file /usr/libexec/evl/tests/ptrace-sync
/usr/libexec/evl/tests/ptrace-sync: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-x86-64.so.2, BuildID[sha1]=7b1a13b097bccaf82b65d49b221ef8c0dd450887, for GNU/Linux 5.15.0, with debug_info, not stripped
Stripping the ptrace-sync executable may be the actual cause of the
issue.
--
Philippe.
next prev parent reply other threads:[~2026-01-23 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 11:42 [PATCH libevl 1/2] tests: ptrace-sync: skip SOH and STX in pipe message Junxiao Chang
2026-01-23 13:22 ` Philippe Gerum
2026-01-24 11:42 ` [PATCH libevl 2/2] tests: ptrace-sync: only integrate ptrace-sync in debug build Junxiao Chang
2026-01-23 13:28 ` Philippe Gerum [this message]
2026-01-26 0:15 ` Chang, Junxiao
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=87ecng1ms9.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=junxiao.chang@intel.com \
--cc=xenomai@lists.linux.dev \
--cc=yuan1.wang@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.