On 10/11/2015 16:04, Claude Frantz wrote:
> My idea was to try to locate which processes are running, which ones are
> dead, where the instruction pointer is, in every process, what is in the
> stack, etc. My idea was to give you this information. Because of the
> multiple processes, it is probably not easy to find this information
> using gdb.
Hi Claude,
you can attach gdb to a running process and then use it to examine the
stack of each thread. It helps a lot of the debug configuration of the
build is used since it has all the local symbol names. To attach gdb to
a running process:
$ gdb -p <pid>
then you can list the threads:
(gdb) info threads
and for a given thread show the current stack trace back for example:
(gdb) thread 1
(gdb) bt
but the information may be of limited use since the main GUI thread will
be sitting in its event loop wait if the GUI is still reactive. If the
application is completely frozen the the information will be valuable
since the main thread stack trace will indicate which function is looping.
73
Bill
G4WJS.
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
