Randolph Chung schrieb:
run your app under gdb; when it hangs, hit ctrl-c and look at the
backtrace. might be able to tell something from the caller...
This is from partimage running under testing-glibc (aka 2.3.2-9)
-><---
[EMAIL PROTECTED]:~$ export LD_LIBRARY_PATH=/usr/lib/debug/
[
just found these on ebay... description says "Hard Drive and Memory
capacity is unknown"
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3439441812&category=177
some info on system available here:
http://www.openpa.net/systems/galaxy.html
might make for a good box to use for demos at conventi
On Wed, Nov 05, 2003 at 08:03:27AM +0100, Ruediger Scholz wrote:
> (gdb) run
> The program being debugged has been started already.
> Start it from the beginning? (y or n) y
> Starting program: /usr/sbin/partimage
> (no debugging symbols found)...
> Program received signal SIGINT, Interrupt.
> 0x40
On Wed, Nov 05, 2003 at 03:21:10PM +, Matthew Wilcox wrote:
> On Wed, Nov 05, 2003 at 08:03:27AM +0100, Ruediger Scholz wrote:
> > (gdb) run
> > The program being debugged has been started already.
> > Start it from the beginning? (y or n) y
> > Starting program: /usr/sbin/partimage
> > (no deb
Matthew Wilcox schrieb:
Try 'bt' for backtrace, that at least tells us where sched_yield()
is being called from.
OK, I tried 'bt' before but I got no useful output as you will see
below. But now I tried 'bt full' and I get a lot of information. Hope
it's more useful...
--><---
[EM
On Wed, Nov 05, 2003 at 07:21:15PM +0100, Ruediger Scholz wrote:
> Matthew Wilcox schrieb:
>
> >
> >Try 'bt' for backtrace, that at least tells us where sched_yield()
> >is being called from.
> >
> OK, I tried 'bt' before but I got no useful output as you will see
> below. But now I tried 'bt ful
6 matches
Mail list logo
