| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/920520
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
| |
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
Add a new USE flag for this (pulling the whole elfutils in if set),
and make it mutually exclusive with unwind because src_configure fails
if both unwinders have been selected.
Closes: https://bugs.gentoo.org/903643
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
| |
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
First attempt to move away from Debian tarballs and towards the somewhat
revived upstream. Unfortunately upstream has yet to release any versions
newer than 0.7.3 so we have to use a git snapshot for that. The suffix
_pre, with the date being that of the chosen commit, has been added
because the version number 0.7.91 got set in the repository almost a
decade ago and it is unknown at this point whether upstream intends to
increment it before the next release or not, assuming they ever make
one.
Tests are still restricted because even though they do not fail as badly
as 0.7.3 ones, all the reasons for having restricted them in the first
place remain valid.
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Effectively abandoned upstream (no git activity in testsuite/ since late
2015 apart from the merging of two arm64-related Fedora patches) and not
run by their CI. EXTREMELY fragile.
Upstream appears to have got a bit more alive in 2022 so let's hope they
will sort this out before ltrace stops working altogether.
Bug: https://bugs.gentoo.org/894386
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
|
|
| |
In case they either add the third component or go back to a single one.
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
| |
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
According to glibc documentation, the syscall employed by the function
fstatat() is only called newfstatat() "on some architectures" (which
happens to include amd64); everywhere else it is called "fstatat64()".
Bug: https://bugs.gentoo.org/809890
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/552720
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-3.0.20, Repoman-3.0.2
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On modern kernels with the Yama security module enabled the default
ptrace behaviour is that a process must have a predefined relationship
with the inferior it wants to call ``PTRACE_ATTACH`` on, with two
additional modes restricting process tracing even more; for details see
[1]. As a result, unless Yama is explicitly reset to classic ptrace
permissions the ltrace attach-process test fails due to
insufficient permissions - regardless of the sandbox, or even when the
test suite is run manually with no involvement of a Gentoo package
manager.
We could in principle modify the test in question to be compatible with
restricted-ptrace mode, however it would still fail on systems with
Yama in admin-attach and no-attach mode. Between that and requiring the
user to reconfigure Yama prior to running this test being IMHO a Bad
Idea, just don't bother with this test at all.
[1] https://www.kernel.org/doc/html/latest/admin-guide/LSM/Yama.html
Closes: https://bugs.gentoo.org/729046
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
Debian now uses two-part version numbers for their changes in this
package, which is not allowed with _p in Gentoo - so just extend the
standard version number by two more parts, it's unlikely this will
conflict with the upstream scheme even if they even do release a new
version.
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
| |
Signed-off-by: Marek Szuba <marecki@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-3.0.17, Repoman-3.0.2
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-3.0.14, Repoman-3.0.2
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.101, Repoman-2.3.22
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.101, Repoman-2.3.22
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.101, Repoman-2.3.22
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
|
|
|
|
|
|
|
| |
Reported-by: Toralf Förster
Closes: https://bugs.gentoo.org/713428
Package-Manager: Portage-2.3.94, Repoman-2.3.21
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.78, Repoman-2.3.17
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
|
| |
Reported-by: Wim Muskee
Closes: https://bugs.gentoo.org/698826
Package-Manager: Portage-2.3.78, Repoman-2.3.17
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.78, Repoman-2.3.17
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
| |
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
| |
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11
RepoMan-Options: --include-arches="ppc"
|
|
|
|
|
| |
Signed-off-by: Mikle Kolyada <zlogene@gentoo.org>
Package-Manager: Portage-2.3.49, Repoman-2.3.11
|
|
|
|
|
| |
Package-Manager: Portage-2.3.51, Repoman-2.3.11
Signed-off-by: Thomas Deutschmann <whissi@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
print-instruction-pointer occasionally fails when
kernel loads test at address that does not match
last 4 digits of 'objdump' output.
On x86_64 page size is 4096 bytes (0x1000). This gives
only 3 digits of stable address.
The change picks last 3 digits from objdump address.
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
Package-Manager: Portage-2.3.50, Repoman-2.3.11
|
|
|
|
|
|
|
|
| |
domhnall noticed old homepage is not working after alioth turndown
and proposed https://www.ltrace.org/. Looks good!
Reported-by: domhnall
Package-Manager: Portage-2.3.42, Repoman-2.3.9
|
| |
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/5817
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
| |
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
|
|
|
|
|
|
| |
Builds successfully on gcc-5.4.0 and can trace
calls to calls like 'gcc -v'.
Package-Manager: portage-2.3.0
|
|
|
|
| |
Package-Manager: portage-2.2.28
|
| |
|
|
|
|
|
|
|
| |
Reported by: Diego Elio Pettenò
Bug: https://bugs.gentoo.org/421649
Package-Manager: portage-2.2.27
|
|
|
|
| |
Package-Manager: portage-2.2.27
|
|
|
|
|
| |
Replace all uses of herd with appropriate project maintainers, or no
maintainers in case of herds requested to be disbanded.
|