Re: Partimage: Problem with sched_yield()
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)
-----><-----------
ruediger@gandalf:~$ export LD_LIBRARY_PATH=/usr/lib/debug/
ruediger@gandalf:~$ gdb /usr/sbin/partimage
GNU gdb 5.3-debian
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "hppa-linux"...(no debugging symbols found)...
(gdb) run
Starting program: /usr/sbin/partimage
(no debugging symbols found)...
Program received signal SIGINT, Interrupt.
0x401a79bc in nanosleep () from /usr/lib/debug/libpthread.so.0
(gdb) Quit
(gdb)
(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.
0x4068cd88 in sched_yield () from /usr/lib/debug/libc.so.6
(gdb) Quit
(gdb)
--------><---------
Sorry, I not so firm with gdb. So where and how can I look up the
meanings of these hex numbers? Or is this enough for you to track down
this pb?
randolph
Ruediger
Reply to: