search

jerrytaffy / conque

Automatically exported from code.google.com/p/conque
0 stars 0 forks source link

Vim exits catching deadly signal HUP #100

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Open vim
2. Execute :ConqueTerm bash<cr> (python, gdb whatever)
3.

What is the expected output? What do you see instead?
Shell is started inside vim
But, instead:
Vim: Caught deadly signal HUP
Vim: Finished.
Hangup

What version of the product are you using? On what operating system?
Arch linux,
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 10 2013 21:30:14)
Included patches: 1-1287
Compiled by Arch Linux

Please provide any additional information below.
This happens only on my laptop. Vim on desktop doesn't suffer from this.

Original issue reported on code.google.com by sakh...@gmail.com on 10 Aug 2013 at 6:36

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Tracked the bug down to the pty allocation in conque_subprocess.py.
The call to pty.fork() raises exception "out of pty devices", returning before 
execvp(). Then vim acts as if the child has died.

Now, is is no more a bug of ConqueTerm, but merely a request to get a 
notification instead of SIGHUP sent to the parent vim.

Original comment by sakh...@gmail.com on 11 Aug 2013 at 7:44