StonedRightMeow17 / mobileterminal

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

blank screen after nmap command #120

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. running any nmap command
2.
3.

What is the expected output? What do you see instead?
I get expected output initially.  After one nmap command the text is no
longer visible.

What version of the product are you using? On what operating system?
Terminal 316s-7
nmap 4.76-5
iphone update 2.2 (not 2.2.1)

Please provide any additional information below.

I have tried reinstallingn both the terminal and nmap.  I have also tried
changing the colors of the text and background in the terminal preferences.
 I know the commands still work because if I type something and then hit
enter I get output.  However the cursor doesn't move nor does any text
appear.  I have only had this problem when I run a command through nmap. 
Any suggestions would be greatly appreciated as it is a huge pain when
typing some of these nmap commands not to be able to see what I am typing.  

Original issue reported on code.google.com by jlud...@gmail.com on 29 Jan 2009 at 12:38

GoogleCodeExporter commented 8 years ago
I can say I am experiencing the same problem.  my product versions are all the 
same, 
and the symptoms are the same.  I too have reinstalled MobileTerminal, and it 
still 
occurs.

Original comment by pjmcgar...@gmail.com on 25 Feb 2009 at 6:41

GoogleCodeExporter commented 8 years ago
I have the same issue on the 2g ipod touch, jailbroken with quickfreedom.  
latest 
mobileterminal and nmap.

Original comment by robot...@gmail.com on 20 Mar 2009 at 12:33

GoogleCodeExporter commented 8 years ago
I have os 3.1.2 and I get the same problem. I don't understand why nmap would 
cause this to happen 
but it seems like an unusual bug. I might just download the source and fix it 
my self (or give it my best 
effort)

Original comment by craby...@gmail.com on 10 Dec 2009 at 6:38

GoogleCodeExporter commented 8 years ago
I'm on firmware 3.1.3 and can corroborate. I have the latest mobile terminal 
and nmap
packages. It outputs nmap commands flawlessly, but the text disappears after the
first nmap command. 

Original comment by mitsuhid...@gmail.com on 21 Mar 2010 at 5:45

GoogleCodeExporter commented 8 years ago
I have a similar issue with 3.1.3 on iPod touch 1G. Jalbroken with PwnageTool. 
Tried to do the command 
"nmap -O 192.168.1.1. Sits for about a second, then Terminal crashes and I get 
a respring. I notices that 
with "Show free memory" turned on in SBSettings, I go from 45MB to 2MB right 
after running the 
command. Then it crashes and resprings. Probably a low memory issue? 

Original comment by espos...@gmail.com on 30 Apr 2010 at 2:54

GoogleCodeExporter commented 8 years ago
this sounds like a bug in the program "nmap". try looking for a bug report 
place for the maintainers/developers of that app for the ipod/iphone. 

Original comment by RethinkR...@gmail.com on 7 Dec 2010 at 2:34

GoogleCodeExporter commented 8 years ago
Nope, it's not, because when running on SSH, it behaves normally.
Therefore, there must be a bug in the executing environment....which is our 
beloved MobileTerminal

Original comment by dave.sto...@gmail.com on 7 Dec 2010 at 2:37

GoogleCodeExporter commented 8 years ago
I stand corrected. can we mark this as accepted?   

Original comment by RethinkR...@gmail.com on 7 Dec 2010 at 3:52

GoogleCodeExporter commented 8 years ago
I've marked it as accepted.  My guess is that its something buggy in the 
VT100Screen/VT100Terminal classes.

Original comment by allen.po...@gmail.com on 7 Dec 2010 at 4:00

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Anyone able to reproduce this in the simulator with the latest revision from 
source? I just installed nmap 5.21 and ran "nmap 10.0.1.1" against my router 
and after the output is displayed everything behaves normally.

Other thoughts:
- I can try on a device as it doesn't happen with the simulator
- This happened to get fixed as a side effect of another bug that I fixed
- This is not an issue for nmap 5.21

Original comment by allen.po...@gmail.com on 18 Jan 2011 at 4:24