Thanks for the feedback and quick turnaround.
-Josh
On Tue, 2006-10-17 at 11:52 -0400, Dave Anderson wrote:
Hi Josh,
I've fixed this one, and queued it for the next release.
The warning messages themselves were bogus because they were
referring to non-existent user-mode-to-kernel-mode exception
frames for each of the kernel threads.
Thanks for the bug report,
Dave
Joshua Giles wrote:
>
> Not quite sure if this or the kdump list is appropriate for this
> discussion, but I will start here...
>
> I've been playing with xen dumping on x86_64 and x86 (RHEL5 20061006.2);
> The following is a simple crash session on x86_64 (using "xm dump-core
> -L"):
>
> `crash /usr/lib/debug/lib/modules/2.6.18-1.2714.el5xen/vmlinux /xen/dump/Live_Dump`
>
> "WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
> WARNING: possibly bogus exception frame
>
>
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility