Re: remote dwarf info using libunwind

[Mike Cvet <mcvet at redhat dot com>]

On Wed, 2006-09-06 at 11:10 +0200, Mark Wielaard wrote:
> On Wed, 2006-09-06 at 01:06 -0400, Andrew Cagney wrote:
 
> > Unfortunatly having frysk use the ptrace calls found in 
> > libunwind-ptrace.a would be wrong.  All ptrace calls to an attached 
> > process must be routed through a single thread and libunwind code won't 
> > be executed within that thread; and would immediatly limit frysk to 
> > native only.  If you think the ptrace limitation is lame then argue it 
> > out with the kernel developers.
> 
> We could make the PtraceThread more general so you can schedule any code
> for execution on it, not just direct ptrace calls. Then you could wrap
> any code that depends on ptrace calls into a Runnable and just put it on
> the PtraceThread run queue.
> 
> Cheers,
> 
> Mark
> 

Since the ptrace thread was essentially just a workaround for #2595 to
address problems with ptrace, I'm not sure if it would be a good idea to
have more dependencies on this thread if we can avoid it. Hopefully this
thread will disappear altogether in the future via utrace.

That being said, I'll take a working solution right now if it means work
can get done immediately on stacktraces, as long as it'll get fixed up
properly later.

- Mike