[Gluster-devel] debugging syntasks

[Jeff Darcy]

On 05/04/2013 03:30 AM, Anand Avati wrote:
> Summarizing some steps which might help others who are debugging
> synctask related issues. Since synctasks uses swapcontext() to switch
> among themselves, the pthread stack would only be representing the
> current executing tasks stack alone (which usually would be the
> syncenv_processor() scheduler.) To inspect the "stack backtrace" of
> other synctasks:
> 
> 0. Attach gdb to the live running (possibly deadlocked or hung) process.
> This approach does not work on a core dump (there might be a way to
> apply the same principles on a core dump, any suggestions welcome)
> 
> ...


Is there any reasonable way to get such listings for *all* synctasks?
That would probably be pretty handy.  I suppose I should put my
collection of Gluster-related gdb macros on the forge or something, and
I could include this.  Thanks!