This is the mail archive of the
insight-prs@sourceware.org
mailing list for the Insight project.
Re: insight/346: insight-6.8-1: Clicking 'Stop' button on Insight GUI warning " Program recieved signal SIGINT, interrupted"
- From: kseitz at sources dot redhat dot com
- To: insight-gnats at sourceware dot cygnus dot com, insight-prs at sources dot redhat dot com, ken at kenm dot demon dot co dot uk, kseitz at sources dot redhat dot com, nobody at sources dot redhat dot com, siva221 at gmail dot com
- Date: 29 Apr 2010 20:18:27 -0000
- Subject: Re: insight/346: insight-6.8-1: Clicking 'Stop' button on Insight GUI warning " Program recieved signal SIGINT, interrupted"
- Reply-to: kseitz at sources dot redhat dot com, insight-gnats at sourceware dot cygnus dot com, insight-prs at sources dot redhat dot com, ken at kenm dot demon dot co dot uk, kseitz at sources dot redhat dot com, nobody at sources dot redhat dot com, siva221 at gmail dot com, insight-gnats at sources dot redhat dot com
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