Hi kgdb folks, Could you please help me understand how the 'ssb' instruction works?
I did some tries on my 64b core i3 and it seems to behave "just" like an 'ss' instruction; stepping all instructions one by one that is. Now, looking at the code I do see an additional DOING_SSB state flag, and I see hints in the kdb_ss comments of the intended behavior: "For 'ssb', set the trace flag in the debug trap handler after printing the current insn and return directly without invoking the kdb command processor, until a branch instruction is encountered." ...but apart from that, the code path for 'ssb' looks to me exactly like the code for 'ss', ending in 'gdbstub_state(ks, "s");' (Also, I don't see how the code could "print the current insn" as mentioned in the comments; even the 'id' command is not there.) I am puzzled. Maybe those are "historical remains" of the "out of tree" kdb patch? Has anybody used the 'ssb' command successfully already, please? Any advice or historical explanations welcome :) Best regards, V. ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
