From: geneSmith <gene.smith@sea.siemens.com>
To: insight@sources.redhat.com
Subject: Stop sign ignored while debugging linux pgm
Date: Fri, 25 Mar 2005 19:53:00 -0000 [thread overview]
Message-ID: <d21q5r$k7c$1@sea.gmane.org> (raw)
I have a program (written by someone else) that I need to look at with
gdb. The program runs in a tight loop looking for a keypress and
servicing tcp/ip events with select. When the program runs under insight
it seems to remove all the oxygen from the insight gui in that the STOP
button and other menus are ineffective. The program itself responds to
the keypresses appropriately. Also, if a window covers the insight gui
with the program running under its control it never get redrawn.
When the program runs stand-alone (with insight/gdb) it does not respond
to ctrl-c. Do I possibly need some sort of SIGINT handler?
When I write my own program just looping forever on printf it responds
to the STOP button (SIGINT) as expected and stops the program
executation as I would expect. But the other program program does not.
Tks,
-gene
--
Lit up like Levy's
next reply other threads:[~2005-03-25 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 19:53 geneSmith [this message]
2005-03-26 0:14 ` geneSmith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='d21q5r$k7c$1@sea.gmane.org' \
--to=gene.smith@sea.siemens.com \
--cc=insight@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).