Re: How to interrupt a stepping GDB ?

Re: How to interrupt a stepping GDB ?

[Daniel Jacobowitz]

On Sun, Jun 18, 2006 at 11:55:19AM +0200, Sascha wrote:
> On a local, fast machine this might be okay. But on a (slow) remote target,
> stepping a loop like this will take minutes or hours because GDB sends
> thousands or even millions of step commands until a == 0;

[The correct fix for this is to add a "step range" packet, which will
speed up the process immensely.  As it happens, I hope to do that for
the next version of GDB after 6.5.]

> Now the question: If I notice such a case - how can I interrupt GDB? If I
> notice that the stepping would take a long time I'd rather interrupt GDB and
> set a breakpoint on the next line. CTRL-C does not work. And waiting hours
> or shutting down GDB is no acceptable.

Breakpoint 1, main () at loop.c:3
3         int a = 200000;
(gdb) s
4         for (; a; --a);
(gdb) n

Program received signal SIGINT, Interrupt.
0x000000000040043c in main () at loop.c:4
4         for (; a; --a);

CTRL-C works for me...

-- 
Daniel Jacobowitz
CodeSourcery

Re: How to interrupt a stepping GDB ?

[Jim Blandy]

Daniel Jacobowitz <drow@false.org> writes:
> On Sun, Jun 18, 2006 at 11:55:19AM +0200, Sascha wrote:
>> On a local, fast machine this might be okay. But on a (slow) remote target,
>> stepping a loop like this will take minutes or hours because GDB sends
>> thousands or even millions of step commands until a == 0;
>
> [The correct fix for this is to add a "step range" packet, which will
> speed up the process immensely.  As it happens, I hope to do that for
> the next version of GDB after 6.5.]
>
>> Now the question: If I notice such a case - how can I interrupt GDB? If I
>> notice that the stepping would take a long time I'd rather interrupt GDB and
>> set a breakpoint on the next line. CTRL-C does not work. And waiting hours
>> or shutting down GDB is no acceptable.
>
> Breakpoint 1, main () at loop.c:3
> 3         int a = 200000;
> (gdb) s
> 4         for (; a; --a);
> (gdb) n
>
> Program received signal SIGINT, Interrupt.
> 0x000000000040043c in main () at loop.c:4
> 4         for (; a; --a);
>
> CTRL-C works for me...

Maybe this has been discussed before, but:

Should 'step' stop stepping if the PC fails to make forward progress?
In every situation I can think of, that would mean that a loop
iteration has been completed.  It shouldn't affect loops that cover
more than one line.

But it might be confusing to the user: "I told it to step, and nothing
happened!"

Re: How to interrupt a stepping GDB ?

[Mark Kettenis]

> From: Jim Blandy <jimb@codesourcery.com>
> Date: Mon, 03 Jul 2006 11:28:46 -0700
> 
> Maybe this has been discussed before, but:
> 
> Should 'step' stop stepping if the PC fails to make forward progress?
> In every situation I can think of, that would mean that a loop
> iteration has been completed.  It shouldn't affect loops that cover
> more than one line.

I think that's wrong; "step" operators on a line-level, not statement
level.

> But it might be confusing to the user: "I told it to step, and nothing
> happened!"

I think that would indeed be a problem.

The solution for the problem is to change the source code such that
there actually is a statement inside the loop:

  while(a)
    a--;

or perhaps

  for (; a; a--)
    ;

will even work.

Mark

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha

How to interrupt a stepping GDB ?

[Sascha]

Hello,

I've got a question about GDB and the "next/step" command.

Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"

This is a simple loop counting down to zero.

If you "next", GDB will step through that loop until a == 0.

On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;

Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.

Thanks

Sascha