| commit | d0bc5b725dac852764b98b9b3e0560c003bd000a | |
| author | Gabriel F. T. Gomes <gabrielftg@linux.ibm.com> | |
| Wed, 4 Dec 2019 01:40:38 +0000 (3 22:40 -0300) | ||
| committer | Gabriel F. T. Gomes <gabrielftg@linux.ibm.com> | |
| Wed, 4 Dec 2019 12:17:06 +0000 (4 09:17 -0300) | ||
| tree | b76ba20acf3698d8a7107aaa4ea8d7dcbb8a0954 | treesnapshot (tar.gz zip) |
| parent | 6ef1bab699eb82ad24d52a4a045bceb4f7533a5b | commitdiff |
Do not use ld.so to open statically linked programs in debugglibc.sh
Debugging programs that have been dynamically linked against an
uninstalled glibc requires unusual steps, such as letting gdb know where
the thread db library is located and explicitly calling the loader.
However, when the program under test is statically linked, these steps
are not required (as a matter of fact, using the dynamic loader to run a
statically linked program is wrong and will fail), and gdb should be
called the usual way.
This patch modifies debugglibc.sh so that it checks if the program under
test is statically linked, then runs the debugger appropriately.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
Debugging programs that have been dynamically linked against an
uninstalled glibc requires unusual steps, such as letting gdb know where
the thread db library is located and explicitly calling the loader.
However, when the program under test is statically linked, these steps
are not required (as a matter of fact, using the dynamic loader to run a
statically linked program is wrong and will fail), and gdb should be
called the usual way.
This patch modifies debugglibc.sh so that it checks if the program under
test is statically linked, then runs the debugger appropriately.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
| Makefile | diffblobblamehistory |