This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Ah, now I see. You didn't mean "That doesn't work", you meant "That doesn't work generally".
#1 doesn't apply to us at Apple. #2 is a real problem - although
the failure mode is that the UI re-fetches the stack, so it's not
too traumatic. And because it only needs to re-fetch the 0th frame,
it is fast. And you'll have the same problem with varobj's being
deleted when your FP moves IIRC.
As for #3, I don't understand why the PC won't remain constant for a frame other than the 0th, but you're familiar with far more architectures than me. Obviously the currently executing frame will have a changing PC, but the frames higher up on the stack should stay constant unless they've executed some more.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |