RE: gdb single stepping takes ages

> Just after sending the mail recognized that the thread: "Remote Debugging with
> NEXT Command" touches a similar (the same?) issue. A solution mentioned was
> range checking. But in the openocd case it seems already enabled:
> show range-stepping
> Debugger's willingness to use range stepping is on.
> 
This command shows the "willingness" not if it is actually enabled:

(gdb) show range-stepping
Debugger's willingness to use range stepping is on.

(gdb) set range-stepping on
warning: Range stepping is not supported by the current target

Imho, it is a bit confusing.

 -Sanimir

Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052