Re: [Kgdb-bugreport] [PATCH] kgdbts: unify/generalize gdb breakpoint adjustment
Status: Beta
Brought to you by:
jwessel
From: Andrew M. <ak...@li...> - 2009-06-05 04:14:07
|
On Fri, 5 Jun 2009 00:00:22 -0400 Mike Frysinger <vap...@gm...> wrote: > your version after all requires every arch to copy & paste this crap: > static inline unsigned long instruction_pointer(struct pt_regs *regs) > { > return regs->ip; > } > static inline void instruction_pointer_set(struct pt_regs *regs, > unsigned long val) > { > regs->ip = val; > } > > and then actual usage turns into: > instruction_pointer_set(regs, instruction_pointer(regs) + foo); > > whereas mine is two lines: > #define instruction_pointer(regs) ((regs)->ip) > instruction_pointer(regs) += val; The aim isn't really to reduce the amount of typing one needs to do. Let's get things right, and if getting it right involves more typing then so be it. If it really worries you then you could do #define GET_IP(regs) ((regs)->ip) #include <asm/generic/instruction_pointer.h> and static inline unsigned long instruction_pointer(struct pt_regs *regs) { return GET_IP(regs); } static inline void instruction_pointer_set(struct pt_regs *regs, unsigned long val) { GET_IP(regs) = val; } Note that GET_IP() is all-caps, which says "this is a macro". But I don't think it's worth the ickyness, unless we also incorporate kernel_stack_pointer(), frame_pointer(), user_stack_pointer() and perhaps the _set() versions of those also. Do we know how to implement instruction_pointer_set() on ia64, btw? |