This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: pausing gdb

From: Andrew Cagney <cagney at gnu dot org>
To: Qing Zhang <qzhang at cs dot utah dot edu>
Cc: gdb at sources dot redhat dot com
Date: Wed, 04 Aug 2004 20:24:42 -0400
Subject: Re: pausing gdb
References: <Pine.GSO.4.50L0.0408041707180.7882-100000@faith.cs.utah.edu>

Hi,

Can anyone tell me how ctrl-c is handled in gdb?  More importantly how
is gdb able to continue from a sigint.

your help is much appreciated.

I'm assuming this is UNIX. Check the man pages for ptrace, and wait. The sequence, assuming that GDB's attached to the process (aka inferior):

- GDB's blocked on wait() ; inferior process running - user enters CNTRL-C - kernel, instead of delivering cntrl-c to inferior process, unblocks GDB returning a ``SIGINT'' indication for that wait() call - GDB interacts with user - user enters "continue" - gdb does ptrace (continue) - kernel resumes inferior process (signal is never delivered)

Andrew

References:
- pausing gdb
  - From: Qing Zhang

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]