Menu

#18 arm - fix bad syscall error from execve()

open
nobody
None
5
2005-10-25
2005-10-25
Anonymous
No

When the strace'd program is run by execve(), strace
gets an SIGTRAP with the program's initial state. This
causes an error, as there is often no SWI instruction
at the start, and thus a bad syscall is reported.

Discussion

  • Nobody/Anonymous

    Logged In: NO

    Change by Ben Dooks, ben-linux@fluff.org

     
  • Mikael Pettersson

    Logged In: YES
    user_id=176526

    Thank you for this patch. Without it, strace-4.5.14 fails
    as you describe for every program on my glibc-2.3.3 based
    Linux/ARM system. With the patch, strace seems to be working
    as expected.

     
  • Thomas Giesel

    Thomas Giesel - 2007-09-21

    Logged In: YES
    user_id=443596
    Originator: NO

    I would also recommend to add this patch to the baseline. Wonder why it isn't already in 4.5.16...

    Thomas

     
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.