David,
Kyle is correct, it is a long standing 2.6 change. The magic-dir is
there for compatibility, seeing those accesses in traces when the
corresponding directory doesn't exist makes things most confusing. The
correct path is /proc/PID/task/TID.
I'd assume this was a side effect of the NPTL and related changes which
led to linux getting working threads.
Andrew
David Mosberger-Tang wrot
While I was searching this out, I found another strange issue. When
libunwind goes to look in the /proc/PID/maps info, it always assumes
that /proc/PID/maps exists, even for subsidiary threads of a single
process. Though this data exists, likely for legacy compatibility with
2.4 kernels, it seems unwise to rely on it always being there.
That would be news to me. In the past, Linus always advocated
"intelligent" threads and removing /proc/PID/maps from "threads" would
be quite contrary to that mantra. Maybe this changed, but if so, I
certainly haven't heard about it. In other words, I don't think this
is something we need to change, but if somebody has info to the
contrary, I'd certainly like to hear about it.
Thanks,
--david
_______________________________________________
Libunwind-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/libunwind-devel
