Hi,
> By interpreting the 1st argument as an address and reading the value on this
> address, I get a 0 for the first three lines of my output (which are the
> futex calls).
No surprise for the first one because you just pushed a 0 at it to
unblock your process.
For the later ... I just wonder
Hi,
1) To have a less cryptic output you may add one function to your
program.
It is composed of an automatically built part from header (on my
system /usr/include/asm/unistd_32.h) sc.h file and
a C source file that includes the former.
a) Building the sc.h by :
awk 'NR==1 { printf("#include <%s>
> You are right. I dont need to restore the signal handler - one system call
> less in my signal handler.
> I now saved a snapshot of the unfinished futex call. So I can experiment as
> often as I want.
> Poking a 1 does not work. But Poking a 0 works perfektly fine.
Thank you for this informati
Yes yes ! Normally the connect(2) should be followed by a send(2).
It is impossible to strace and use survfutex at the same time on your
process because both of them use the ptrace(2) and a process cannot be
ptraced twice at the same time (the ATTACH will not work).
But, you can use the tcpdump co
Hi,
> Basically my program looks like this:
>
> static volatile sig_atomic_t child_terminated=0;
>
> void sigchld_handler(int sig) {
> int copy_errno=errno;
> debug("Received SIGCHLD");
> child_terminated=1;
> signal(SIGCHLD,sigchld_handler);
> errno=copy_errno;
> }
>
> int
Hi Wayne,
A - There are some "strange" behaviours with signal on Linux since the
advent of posix threads. I mean "strange" for programer that is used
with the simple fork()/wait()/exit().
What I just concluded with all of this, is :
if one choose to use this then he has to avoid using s
Hi,
When you try to quit, do you use an Interrupt key sequence (i.e.
Ctrl-C) ?
-Rogers
> I know almost nothing about this, but I am seeing the same error in
> xmoto. I try to quit and it hangs until I kill it with -9. Strace
> reveals a futex hang. 100% reproducible. Hardy Heron with fglrx.
>
>
Hi,
I am experiencing same trouble on a self made program.
I made a tool used to unfreeze process (and watch periodically) : survfutex
I send you the source in attachment. You can try it on the frozen process to
check that it works (normaly it would). It is using the ptrace(2) syscall to
attach t
