Re: Stuck gnat1 processes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Thu, 09 Jun 2011, Carlos O'Donell wrote:

> This looks like a combination of multiple bugs, the process is
> probably dead, or not running, which is why gdb can't do anything with
> it. I'm surprised the ptrace API isn't returning some more diagnostics
> about the stuck process.

Why do you think the processes are dead or not running?  Top thinks
they are running at 100% CPU.  The general system responsiveness
seemed like full load.

The backtraces indicated that a diagnostic report was in process of
being output.  The $r19 register appears to point to the expected location.
Possibly, there is a space register mixup but gdb doesn't show them
correctly.  I think x/x $r19 worked ok.

There is no indication that the processes are waiting for anything.

Gnat1 would normally do a compilation and exit.  I don't believe it
is multithreaded.

Strace showed nothing.  Gdb always attached at the same location.

It was possible to kill the processes, and then make terminated when
the last process was killed.

Dave
-- 
J. David Anglin                                  dave.anglin@xxxxxxxxxxxxxx
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Free Online Dating]     [Linux Kernel]     [Linux SCSI]     [XFree86]

Add to Google Powered by Linux