https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70220
--- Comment #19 from Wink Saville <wink at saville dot com> --- (In reply to H.J. Lu from comment #18) > (In reply to Wink Saville from comment #17) > > > > > > I assume you were referring to real debugger, like GDB. Spec won't > > > specify > > > where/how/when any register is saved. > > > > From my perspective the spec defines precisely where the original value of > > every register is, when "all" is present, except rbp. Will you provide that > > info? > > Sorry, this is not how compiler works. > > > If not then as for as I can tell I won't be able to use the interrupt > > attribute for these use cases, which I think is a shame as I really like > > using it. > > > > Well, I guess this feature isn't appropriate for you. > > > Compiler should generate correct debug > > > info when -g is given. GDB should have no problem to access any registers > > > and variables, including interrupt data passed down by processors. > > > > To debug code -g is not needed, I will not be compiling my isr's with -g to > > be able to debug code that resides in another thread/process. > > But to debug code I must know the original value of every register and be > > able to change it to any value the user requests, no exceptions. > > -g with GCC should provide information about all registers and > variables. You can extract debug info into a separate file > to exam it. Oh well, maybe someday, thanks for considering my desires.
