Execute last command on app close

wangxiaoxiang / mobileterminal

Automatically exported from code.google.com/p/mobileterminal

0 stars 1 forks source link

Execute last command on app close #251

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Enter a command in the prompt (e.g., killall -HUP SpringBoard
2. Close the app using the physical home button
3.

What is the expected output? What do you see instead?

MobileTerminal will execute the command upon app close instead of just ignoring 
it, as it should. Benign if you close the app with "ls" I'm sure, but 
problematic if you have a more "invasive" command.

What version of the product are you using? On what operating system?

0.510

Please provide any additional information below.

Allen, I know you don't have a physical phone to test this on, so it may be 
difficult to test. If you need a test subject, I volunteer. All I would need is 
the compiled code as I don't have XCode installed.

Original issue reported on code.google.com by william....@gmail.com on 25 Jan 2011 at 11:05

GoogleCodeExporter commented 8 years ago

Type "command &", then close MobileTerminal
It's the same

Original comment by dave.sto...@gmail.com on 25 Jan 2011 at 1:41

GoogleCodeExporter commented 8 years ago

I was able to reproduce this in the simulator.  Definitely not cool! thanks for 
reporting this.

Original comment by allen.po...@gmail.com on 13 Feb 2011 at 9:31

Changed state: Accepted

GoogleCodeExporter commented 8 years ago

This issue was closed by revision r519.

Original comment by allen.po...@gmail.com on 13 Feb 2011 at 9:46

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

Still not fixed in the 520 release. Same steps to reproduce as above.

Original comment by william....@gmail.com on 16 Feb 2011 at 8:11

GoogleCodeExporter commented 8 years ago

The old 364 revision did not have this problem.
Maybe we shoukd concentrate in porting this rev to 4.x instead?

Original comment by dave.sto...@gmail.com on 16 Feb 2011 at 8:16

GoogleCodeExporter commented 8 years ago

are you're saying we should try to make 364 work on iOS4?  Good luck, anyone is 
welcome to give it a shot.  I haven't heard of anyone who could compile it in 
the last few years (see my pleas to the google groups).  I gave up and started 
re-writing it instead, which also took two years.

Anyway, I re-opened this bug.  Maybe I thought it was fixed, but was just only 
randomly able to reproduce it.  

Are you reproducing this on an iPad or iPhone? What OS version?

Original comment by allen.po...@gmail.com on 17 Feb 2011 at 6:45

Changed state: Accepted

GoogleCodeExporter commented 8 years ago

Well, if it's that hard, maybe we should stick to the rewritten version.
I'll try to summarize all noticable differences between 364 and our current 
builds
Maybe this could make our life easier

Original comment by dave.sto...@gmail.com on 17 Feb 2011 at 6:49

GoogleCodeExporter commented 8 years ago

My vote goes to sticking with Allen's version. It has promise and if he's spent 
that much time rewriting it from scratch, it would be a sheer waste to curb it 
now. These are all minor bugs imho.

Allen, I'm using an iPhone 4, running iOS 4.2.1 with the tethered redsn0w 
jailbreak.

Original comment by william....@gmail.com on 27 Feb 2011 at 8:30