How about gdb attach process_id ?
Or I am missing something?
Regards,
Sandeep.
On Fri, Nov 28, 2008 at 2:25 PM, yogeshwar sonawane <[EMAIL PROTECTED]> wrote:
> Hi all,
> Suppose, I have an application or library code containing following :-
>
> while (expected condition has not occurred)
> {
> handling of expected condition
> }
>
> Now, If the expected condition does not occur, the program goes into
> an infinite loop.
> Now, how to detect this ? For user of the code who is running, it will
> appear as the program got stuck somewhere, not moving ahead.
> But user may not make out that the code is in infinite loop. How such
> info can be derived using some tools like debuggers ?
> I am thinking, whether it is possible to attach a debugger to a
> running code & detect such conditions ? name the debugger also or any
> other tools.
>
> What about similar situation in driver code ?
>
> Any link/reference will be useful.
>
> Thanks in advance,
> Yogeshwar
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to [EMAIL PROTECTED]
> Please read the FAQ at http://kernelnewbies.org/FAQ
>
>
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the FAQ at http://kernelnewbies.org/FAQ