Manoj Kora <[email protected]> writes: > Hi,
Hi, > > I have checkout the latest ltrace source ltrace-0.5.3 in which thread support > is better compared to ltrace-0.5.1. But the thing is that when i use ltrace > to trace an executable containing multi threads on ARM architecture it seems > to be working fine. But the same thing breaks on the MIPS architecture with > the following output: > > pthread_create(0x7f8efca0, 0, 0x400870, 0, 0 <unfinished ...> > pthread_create(0x7f8efca0, 0, 0x400870, 0, 0 <unfinished ...> > pthread_create(0x7f8efca0, 0, 0x400870, 0, 0 <unfinished ...> > pthread_create(0x7f8efca0, 0, 0x400870, 0, 0 <unfinished ...> > pthread_create(0x7f8efca0, 0, 0x400870, 0, 0 <unfinished ...> > pthread_create(0x7f8efca0, 0, 0x400870, 0, 0 <unfinished ...> > > And it never comes of the execution. I have to kill the process to stop the > execution. > > So my questions are: > > 1) Whether MIPS architecture is supported by ltrace-0.5.3 > soruce? (Not in terms of cross compiling but in terms of working of > ltrace on MIPS for multi thread). There are bugs in ltrace on mips. I've sent to the mailing list patches for getting things better some weeks ago. Also, I'm using a mipsel system so I may have missed some endian specific bugs. Regards, Arnaud _______________________________________________ Ltrace-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/ltrace-devel
