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

[Bruce Edge <bruce.edge@xxxxxxxxx>]

Can one build a usable gdbsx from xen-4.0-testing.hg?

Actually a more relevant is, is this still the preferred mechanism for domU kernel debugging?

The documentation on building it is a bit out of date and conflicting.

This post http://blog.xen.org/index.php/2009/10/21/debugging-on-xen/

States that one needs to use this repo: http://xenbits.xensource.com/ext/debuggers.hg

Which looks like hasn't been updated since 4.0 was released as it's still referencing 4.0-rc 

0 %> hg clone http://xenbits.xensource.com/ext/debuggers.hg

destination directory: debuggers.hg

requesting all changes

adding changesets

adding manifests

adding file changes

added 20375 changesets with 117688 changes to 11049 files (+1 heads)

updating working directory

.hgtags@809b20f066fb, line 39: tag '4.0.0-rc1' refers to unknown node

.hgtags@809b20f066fb, line 40: tag '4.0.0-rc2' refers to unknown node

.hgtags@809b20f066fb, line 41: tag '4.0.0-rc3' refers to unknown node

.hgtags@809b20f066fb, line 42: tag '4.0.0-rc4' refers to unknown node

.hgtags@809b20f066fb, line 43: tag '4.0.0-rc5' refers to unknown node

.hgtags@809b20f066fb, line 44: tag '4.0.0-rc6' refers to unknown node

3164 files updated, 0 files merged, 0 files removed, 0 files unresolved

This post: http://zhigang.org/wiki/XenDebugging#xend-debugging

refers to magically generated Oracle images with no information on how they were created or what sources to use.

Other posts state that gdbsx has been integrated into xen-unstable.hg. 

Does that mean all that's needed to build a debug enabled xen image is:

(cd tools/debugger/gdb && ./gdbbuild ) ; 

make kdb=y gdbsx=y && make dist

Thanks

-Bruce

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