[Bug gdb/12709] Stepping on a while loop freezes the GDB (MIPSplatform)

["pedro at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=12709

Pedro Alves <pedro at codesourcery dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |WAITING

--- Comment #3 from Pedro Alves <pedro at codesourcery dot com> 2011-04-27 21:27:24 UTC ---
> The 'c' variable can be changed for example from another thread. From my point
> of view this behaviour can be little uncomfortable for the programmer, because
> when applying the step command the GDB will be frozen until the 'c' is changed.
> This can take very long, because the GDB is just single stepping for all the
> time. (In my case it takes minutes). Thus the programmer is forced to restart
> the debugging session.

The user does not need to restart the debug session.  He can just interrupt the
program, by pressing ctrl-c on the keyboard if debugging on the command line,
or pressing whatever "interrupt" button the IDE gives her.  There is no problem
here.  It's just how things work.

> When I try to reproduce this in standart C desktop application, the GDB will
> stop on the while line after the step command. So I considered the behaviour
> bad.

Please paste a session showing what behavior is different between mips and the
desktop version.  All I can think could be different is when stepping _into_
the bsp_start function _the first time_, the mips version not stopping once
before entering the loop.  That could be a debug info or prologue skipping
issue, for example.  But I'll stop guessing until you paste a better log.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.