This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 193474 - ^C in Pio doesn't have the right effect in remote case
Summary: ^C in Pio doesn't have the right effect in remote case
Status: RESOLVED WONTFIX
Alias: None
Product: cnd
Classification: Unclassified
Component: execution (show other bugs)
Version: 7.0
Hardware: Sun Solaris
: P3 normal (vote)
Assignee: Andrew Krasny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-16 01:37 UTC by ivan
Modified: 2012-10-30 21:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ivan 2010-12-16 01:37:38 UTC
I'm seeing this under dbxtool. Presumably fails under IDE too.
Debug /bin/cat on a remote host (akhmatova is what I tried).

'run' it from dbx console.
Type something in Pio. See it being echoed by cat.
Issue ^D in Pio. See /bin/cat getting terminated correctly.

'run' it again.
Type something in Pio. See it being echoed.
Issue ^C in Pio. Dbx receives "execution completed" instead of 
acting like Pause (signal INT (Interrupt) in _read at 0xff2ca744)
This despite the fact that SIGINT is "caught".

Furthermore a 'run' in dbx cmdline now gives this:
Running: cat 
dbx-dia: open("/dev/pts/1") failed -- No such file or directory
dbx-dia: program could not begin execution
dbx-dia: Cannot start execution

All this works correctly in the local case.
Comment 1 Egor Ushakov 2011-01-21 16:32:55 UTC
looks like execution issue
Comment 2 Leonid Lenyashin 2012-10-30 21:09:41 UTC
There was no activity on this issue for quite a long time. We apologize that the issue was not addressed so far due to lack of development resources. We might not have time in near future to fix this problem, so it is closed as WONTFIX.
If the issue is still critical for you please do not hesitate to REOPEN it.
Thank you for using our product and reporting bugs. We are really sorry that we were not able to fix this issue timely.

Regards,
CND team.