public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/29244] New: [gdb/testsuite, gcc 4.8] Problems with -static and target board unix/-fPIE/-pie
@ 2022-06-11 10:25 vries at gcc dot gnu.org
  2022-06-11 10:31 ` [Bug testsuite/29244] " vries at gcc dot gnu.org
  2023-06-05 14:14 ` vries at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2022-06-11 10:25 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=29244

            Bug ID: 29244
           Summary: [gdb/testsuite, gcc 4.8] Problems with -static and
                    target board unix/-fPIE/-pie
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

On openSUSE Leap 42.3 and gcc 4.8.5, and target board unix/-fPIE/-pie I'm
running into a cluster of FAILs:
...
FAIL: gdb.arch/amd64-disp-step-avx.exp: running to main in runto
FAIL: gdb.arch/amd64-init-x87-values.exp: check_setting_mxcsr_before_enable:
running to main in runto
FAIL: gdb.arch/amd64-init-x87-values.exp: check_setting_x87_regs_before_enable:
running to main in runto
FAIL: gdb.arch/amd64-init-x87-values.exp: check_x87_regs_around_init: running
to main in runto
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: frame
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: starti prompt
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step back into _start (the
program is no longer running)
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step back into foo (the
program is no longer running)
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step into bar (the program
is no longer running)
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step into foo (the program
is no longer running)
...

The problem is that the compilation fails to produces an usable static
executable, instead we get a shared library, and we trying to execute it we run
into "No such file or directory".

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug testsuite/29244] [gdb/testsuite, gcc 4.8] Problems with -static and target board unix/-fPIE/-pie
  2022-06-11 10:25 [Bug testsuite/29244] New: [gdb/testsuite, gcc 4.8] Problems with -static and target board unix/-fPIE/-pie vries at gcc dot gnu.org
@ 2022-06-11 10:31 ` vries at gcc dot gnu.org
  2023-06-05 14:14 ` vries at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2022-06-11 10:31 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=29244

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
More specifically:
...
(gdb) run ^M
Starting program: /data/vries/gdb_versions/devel/build/gdb/testsuite/outputs/g\
db.arch/amd64-disp-step-avx/amd64-disp-step-avx ^M
/bin/bash: /data/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.arch\
/amd64-disp-step-avx/amd64-disp-step-avx: No such file or directory^M
During startup program exited with code 127.^M
(gdb) FAIL: gdb.arch/amd64-disp-step-avx.exp: runto: run to main
...
and:
...
$ file
/data/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.arch/amd64-disp-step-avx/amd64-disp-step-avx 
/data/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.arch/amd64-disp-step-avx/amd64-disp-step-avx:
ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked,
interpreter /lib/ld6, BuildID[sha1]=205ab81333c8b66aaa2a3e2c841f5427145e77ca,
not stripped
...

Possibly the error message corresponds to the missing interpreter:
...
$ readelf -p .interp
/data/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.arch/amd64-disp-step-avx/amd64-disp-step-avx 

String dump of section '.interp':
  [     0]  /lib/ld64.so.1
$ ls -al /lib/ld64.so.1
ls: cannot access '/lib/ld64.so.1': No such file or directory
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug testsuite/29244] [gdb/testsuite, gcc 4.8] Problems with -static and target board unix/-fPIE/-pie
  2022-06-11 10:25 [Bug testsuite/29244] New: [gdb/testsuite, gcc 4.8] Problems with -static and target board unix/-fPIE/-pie vries at gcc dot gnu.org
  2022-06-11 10:31 ` [Bug testsuite/29244] " vries at gcc dot gnu.org
@ 2023-06-05 14:14 ` vries at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2023-06-05 14:14 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=29244

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Likewise, with aarch64-linux I run into:
...
FAIL: gdb.base/break-entry.exp: running to .* in runto
FAIL: gdb.base/catch-fork-static.exp: run to fork
FAIL: gdb.threads/staticthreads.exp: continue to main's call of sem_post
FAIL: gdb.threads/staticthreads.exp: handle SIG32 helps
FAIL: gdb.threads/staticthreads.exp: running to main in runto
FAIL: gdb.threads/staticthreads.exp: running to main in runto
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step back into _start
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step back into foo
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step into bar
FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step into foo
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-06-05 14:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-11 10:25 [Bug testsuite/29244] New: [gdb/testsuite, gcc 4.8] Problems with -static and target board unix/-fPIE/-pie vries at gcc dot gnu.org
2022-06-11 10:31 ` [Bug testsuite/29244] " vries at gcc dot gnu.org
2023-06-05 14:14 ` vries at gcc dot gnu.org

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).