![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On 0, Jerry Feldman <gaf at blu.org> wrote: > I think what you want is the continue command. The continue command > proceeds to the next breakpoint. > Subba Rao wrote: > > > > It has been a long time since I have used the gdb dubugger. > > I am steping through a large program and would like to > > automate the 'next' command from breakpoint A to breakpoint B. > > > > How can I automate the 'next' command in this case? > > > > TIA. > > -- > > Thanks for replying. 'continue' would not shown the execution in sequence for each line of code. It would execute upto breakpoint B and wait for further instructions. I would like to see the 'next' command executed from A to B i.e. to watch the sequence of execution. -- Subba Rao subb3 at attglobal.net http://pws.prserv.net/truemax/ - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |