Dima Kogan <[email protected]> writes: > ./ltrace -L -x xyz /tmp/pie-yjtNlTxFte > > Running that same command with that same executable later worked just > fine. There was some log file that was being generated that had 200MB of > the same error repeated on every line. Something about an illegal or > duplicated breakpoint; don't exactly remember, sorry. Re-running the > test suite didn't show this problem. > > By the way, how much of the suite is supposed to pass normally? I always > see some failures and a segfault. The configuration is Debian/sid on > amd64; nothing noteworthy.
Well, most of it. Different parts on different architectures. I was never very careful to formally state in each test case which arches have that support an which don't, so typically what happens is that I implement a new arch-dependent feature (say, tracing irelative symbols), and the corresponding test only passes on x86_64, with the rest following possibly later. Right now, on my x86_64 installation, I see a SIGSEGV in main-vfork.exp, which I think is fairly new (didn't use to be there, say, half a year ago, I reckon); struct_func_str9 and struct_func_str16 fail in parameters-str.exp--I think those are your new test cases; and wcstold in wchar.exp fails, but that has been there for some time, I just haven't had time to look into it yet. > I just pushed a patch. You were using an older gcc than me, and it's > more picky. Before this patch I successfully tested with gcc 4.9. After, > gcc 4.6 works too. Yep, works now. > I also just discovered that this new symbol aliasing code works with > 'ltrace -l', but not any of the other filtering options. I'll take a > look when i have time; hopefully by next week. OK. Let me know when you are happy with the code. Thanks, PM _______________________________________________ Ltrace-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/ltrace-devel
