Re: Partimage: Problem with sched_yield()
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...
----------><-----------
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.
0x4068cd88 in sched_yield () from /usr/lib/debug/libc.so.6
(gdb) Quit
(gdb) bt
#0 0x4068cd88 in sched_yield () from /usr/lib/debug/libc.so.6
(gdb) bt full
#0 0x4068cd88 in sched_yield () from /usr/lib/debug/libc.so.6
__elf_set___libc_subfreeres_element_free_mem__ = (
const void *) 0x40715db6
empty_set = {alloc = 0, nelem = 0, elems = 0x0}
re_comp_buf = {buffer = 0x0, allocated = 0, used = 0, syntax = 0,
fastmap = 0x0, translate = 0x0, re_nsub = 0, can_be_null = 0,
regs_allocated = 0, fastmap_accurate = 0, no_sub = 0, not_bol = 0,
not_eol = 0, newline_anchor = 0}
stack_pointer = 0xfaf05ec0 ""
__evoke_link_warning_re_max_failures =
"\177ELF\001\002\001\003\0\0\0\0\0\0\0\0\0\003\0\017\0\0\0\001\0\001õ4\0\0\04\001\031¤\230\0\0\002\020\04\0
\0\006\0(\0\\\0Y\0\0\0\006\0\0\04"
re_syntax_options = 0
__re_error_msgid = "Success\0No match\0Invalid regular
expression\0Invalid collation character\0Invalid character class
name\0Trailing backslash\0Invalid back reference\0Unmatched [ or
[^\0Unmatched ( or \\(\0Unmatched \\{\0Invalid "...
re_max_failures = 2000
__re_error_msgid_idx = {0, 8, 17, 44, 72, 101, 120, 143, 161, 179,
192, 216, 234, 251, 288, 324, 351}
(gdb)
--------><-----------
Ruediger
Reply to: