public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: kseitz@sources.redhat.com To: insight-gnats@sourceware.cygnus.com, insight-prs@sources.redhat.com, ken@kenm.demon.co.uk, kseitz@sources.redhat.com, nobody@sources.redhat.com, siva221@gmail.com Subject: Re: insight/346: insight-6.8-1: Clicking 'Stop' button on Insight GUI warning " Program recieved signal SIGINT, interrupted" Date: Thu, 29 Apr 2010 20:18:00 -0000 [thread overview] Message-ID: <20100429201827.28694.qmail@sourceware.org> (raw) Synopsis: insight-6.8-1: Clicking 'Stop' button on Insight GUI warning " Program recieved signal SIGINT, interrupted" Responsible-Changed-From-To: unassigned->kseitz Responsible-Changed-By: kseitz Responsible-Changed-When: Thu Apr 29 20:18:27 2010 Responsible-Changed-Why: mine State-Changed-From-To: open->analyzed State-Changed-By: kseitz State-Changed-When: Thu Apr 29 20:18:27 2010 State-Changed-Why: This could be a problem with gdb itself. If you run "insight -i console" on your executable and you try to interrupt it (with control-c), does it still say "Program received signal SIGINT, interrupted"? If so, you have a gdb bug, and you'll need to ask the gdb folks how to resolve this. Although I must say, 6.8.1 is *ancient*. Have you tried a snapshot or something newer? [I build the repo weekly and use it daily without incident.] http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=346
next reply other threads:[~2010-04-29 20:18 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-29 20:18 kseitz [this message] -- strict thread matches above, loose matches on Subject: below -- 2009-10-20 12:23 siva221
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=20100429201827.28694.qmail@sourceware.org \ --to=kseitz@sources.redhat.com \ --cc=insight-gnats@sources.redhat.com \ --cc=insight-gnats@sourceware.cygnus.com \ --cc=insight-prs@sources.redhat.com \ --cc=ken@kenm.demon.co.uk \ --cc=nobody@sources.redhat.com \ --cc=siva221@gmail.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: linkBe 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).