strace segfaults on mips in a glibc env. the same version built against uclibc does not output anything strace-4.5.7 works in uclibc (do not have access to the glibc version to rebuild) Reproducible: Always Steps to Reproduce: 1. 2. 3.
same thing maybe with CHOST="mipsel-pc-linux-uclibc" and strace-4.5.1 strace prints ')' then exits with error code 1 The ELFs entry_point itself almost seems to be fubar. Portage 2.0.51-r3 (uclibc/mips/mipsel, gcc-3.4.1, uclibc-0.9.27-r0, 2.6.9-mipscvs-20041022 mips) Will test >=dev-util/strace-4.5.7 at a later time.
4.5.7 (does not work) mipsel(root) # strace /bin/ls = ? ERESTARTNOINTR (To be restarted) ------------------------------------ 4.5.8 (does not work) no output. ------------------------------------ 4.5.9 (does not work) no output. mipsel(root) # strace -v -o woof /bin/ls main main.c woof mipsel(root) # wc woof 0 0 0 woof I do appear to be able to PTRACE_ATTACH to a given pid but there is no output with it either. Almost as if PTRACE_SYSCALL and PTRACE_SINGLESTEP do nothing. strace -c ls (causes segfault) Anybody know what the breakpoint op code on mipsel is?
This strace binary package works so the problem is internal http://openwrt.org/downloads/experimental/bin/packages/strace_4.5.9-1_mipsel.ipk
That strace binary packages actually does not work so hot. (gets syscalls and return codes wrong) Now that I think about it, it was cross compiled for 2.4.2x So my guess today is this bug is probably caused by a headers problem on mips(EL?) with 2.6.x
Bug outdated, and not reproducible anymore since that version of the package was removed.