Why? What does that even mean?
An application run under Eclipse shouldn't assume that Eclipse will always be there. Indeed, if you're using Eclipse to run production processing, you're either using the non-IDE aspects of Eclipse (which few do) or you've got some serious management problems.
A child can determine what its stacktrace is by simply creating an Exception and invoking printStackTrace on it. That will run you up to the
thread root. I don't know any way offhand to determine what code constructed or launched a Thread, but then again, when I need to know such things, it's always been in a context where the caller could be designed to provide that information.
