Jeff Layton wrote:
Looks like we might have gotten bitten by some upstream changes
again...
When I run crash on a recent rawhide x86_64 kernel, I seem to be
getting this error:
crash: invalid structure member offset: task_struct_parent
FILE: task.c LINE: 2163 FUNCTION: store_context()
[/usr/bin/crash] error trace: 49150a => 495bb8 => 4963be => 4fc1bc
/usr/bin/nm: /usr/bin/crash: no symbols
/usr/bin/nm: /usr/bin/crash: no symbols
/usr/bin/nm: /usr/bin/crash: no symbols
/usr/bin/nm: /usr/bin/crash: no symbols
Relevant package versions:
crash-4.0-6.2.x86_64
kernel-2.6.25-0.185.rc7.git6.fc9.x86_64
...machine is a x86_64 FV xen guest. Any thoughts?
Thanks,
Hmmm. The task_struct.parent member still exists upstream with
the same name, shown here after a fresh git pull:
/*
* pointers to (original) parent process, youngest child, younger sibling,
* older sibling, respectively. (p->father can be replaced with
* p->parent->pid)
*/
struct task_struct *real_parent; /* real parent process (when being debugged) */
struct task_struct *parent; /* parent process */
If you run "gdb vmlinux" and then do a "ptype struct task_struct", does
it not show the parent member?
Dave
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility
