> PendingFrame.create_unwind_info (frame_id) > 1 file changed, 44 insertions(+), 38 deletions(-) > exact code here, but I think what I'm proposing is less misleading > the function being unwound, it's almost impossible to include more > need to be performed are both architecture specific, and dependent on > comments indicating what needs to be done. > I've removed the incorrect code and replaced it with more generic > 'Unwinder Input' section when describing building a frame-id. > counter is (a) not correct, and (b) counter to what is laid out in the > frame-id was being built (using the current stack point and program > Additionally, in the example skeleton code the way in which the > should be included in the skeleton code, and the example is therefore > reordering the sections, it is now obvious that the registration > one missing line which the user has to figure out for themselves. > users (I think) as the skeleton code is almost complete, except for > registration line in the skeleton code. > section 'Registering an Unwinder' we have skipping including the > Additionally, by placing the 'Unwinder Skeleton Code' before the > 'unwinders' when it should say 'unwinder' in one case. The 'Unwinder Skeleton Code' has an error: it says > The documentation for the Python Unwinders API could do with some Re: gdb/doc: spring clean the Python unwinders documentation - Andrew Burgess public inbox for help / color / mirror / Atom feed From: Andrew Burgess Ĭc: Re: gdb/doc: spring clean the Python unwinders documentationĭate: Tue, 09:27:29 +0000
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |