Re: [Xen-devel] State of gdbsx in xen-4.0-testing.hg and debugger documentation.

[Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>]

> 
> Additionally, there's a problem with the macros in the docs too. After
> sourcing them, the ps command makes gdb exit:
> 
> (gdb) source /users/bedge/macros.gdb
> (gdb) ps
> Pointer       PID      Command
> /build/buildd/gdb-6.8/gdb/printcmd.c:2261: internal-error:
> printf_command: Assertion `*p == 'p' && *(p + 1) == '\0'' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Quit this debugging session? (y or n) [answered Y; input not from
> terminal] /build/buildd/gdb-6.8/gdb/printcmd.c:2261: internal-error:
> printf_command: Assertion `*p == 'p' && *(p + 1) == '\0'' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Create a core file of GDB? (y or n) [answered Y; input not from
> terminal] zsh: abort      gdb ./vmlinux


Seems to be a gdb bug. Replace:

printf "%-14p%-9d%s\n", $task_entry, $task_entry->pid, $task_entry->comm

with 

printf "%p %-9d%s\n", $task_entry, $task_entry->pid, $task_entry->comm


Mukesh



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel