Dave, Thanks for the reply, please excuse the rough formatting, I'll turn the digest off so future exchanges will be better attributed. On 06/28/2012 09:00 AM, crash-utility-request(a)redhat.com wrote: I can appreciate that it's not an easy task, in my limited experience with the source for gdb it seems "venerable and eccentric" :) which must make rebasing a challenge. From my point of view that challenge is increased because I don't immediately have a grasp on the purpose of the patch and therefore how to react to failures to apply some changes. For instance the version I'm looking at would seem to be a snapshot of approximate 7.4.0 heritage, which has done away with some of the patch sites, like rltypedefs.h and cli-cmds.c. The former seems, to me, to be something I can ignore for now; readline makes things nicer to use but isn't vital. However cli-cmds seems more fundamental to basic functionality. All of which is just to say that experience has taught me that before I dive in and try to understand the mating of two unfamiliar components, it's worth asking if anyone has a guide book handy. Because the kernel I'm working with, while sharing a lot of the current x86_64 architecture, doesn't identify itself as such. I've been given access to gdb that's been hacked on to support userspace debug, but I want to play with the kernel. I can't immediately share the source I have, but since it's for internal development only I think my only problem is I get to update crash. So we can continue to use it until we can pass on what's useful to whoever's interested in it. I'm also working on the opposite end, to see if I can get information on the changes made to gdb and determine whether I can backport that into 7.3.1 which, if my understanding is correct, will also allow me to rig crash for my use until the official gdb support gets out.