This is the mail archive of the 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]

testing current target (in gdb code)


I'm currently working on making gdb's v850 support work on real CPUs,
and unfortunately I can't get the hardware single-stepping to work
consistently (the hardware has lots of weird restrictions, and by doing
lots of tricks I can get it to work on some processors, but not others).

So I'd like to use GDB's software-single-stepping facility for those
cases where I can't use hardware (thanks to Kevin Buettner who told me
where to find it!); however, I'd still like to use hardware
single-stepping when possible as it seems likely to always be reliable
in some corner case or another, no matter how careful I am.  In
particular, `hardware' single-stepping works great in GDB's simulator.

I guess I can do this sort of thing by defining SOFTWARE_SINGLE_STEP_P
to call a function that looks at the current target and returns an
appropriate boolean for it (defaulting to 1 I suppose).

However I'm not sure how to test the current target; any pointers?

Or am I on the wrong track entirely, and there's a better way to do
what I want?

Thanks for any tips,

`Life is a boundless sea of bitterness'

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]