| 63753e08aaec64973649fcf17368740bebeea21e |
|
31-Jan-2014 |
Petr Machata <pmachata@apm-mustang-ev2-02.ml3.eng.bos.redhat.com> |
Force use of SYS_open on aarch64 as well
- That system call is not implemented on aarch64, but we don't
care, we are only calling it to see if the parameters get decoded
properly. So call using the "syscall" wrapper, and hard-code
SYS_open value on aarch64, where glibc doesn't define it.
/external/ltrace/testsuite/ltrace.main/system_call_params.exp
|
| 5069ef8f498e5189de0789d79485f39b76c621d4 |
|
24-Oct-2013 |
Petr Machata <pmachata@redhat.com> |
Fix fetching of system call arguments on i386
/external/ltrace/testsuite/ltrace.main/system_call_params.exp
|
| 82f748d1bc2b95d594327ad15f3a6908070dd5c3 |
|
23-Oct-2013 |
Petr Machata <pmachata@redhat.com> |
System calls are now part of dedicated symbol library
- This symbol library is still special in that symbols are created on
demand and never actually added. It just serves as a link to
protolibrary with system call prototypes, and has a name (SYS).
- Prototypes for system calls were moved to a dedicated prototype
library called syscalls.conf.
- Because it's undesirable to look up syscall prototypes in anything
but the dedicated syscall protolib, prototype.c/.h now understand
that some lookups shouldn't be done recursively (and so we never
pick the definition from -F file that just happens to have the same
name as a system call). The good thing is that now libraries can
actually use symbols named SYS_something without clashing with
system call prototypes.
- One test case needed to be updated, because we now display system
calls as something@SYS instead of SYS_something.
/external/ltrace/testsuite/ltrace.main/system_call_params.exp
|