-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nmap -A crashes emacs when simple-httpd is running #10
Comments
Emacs 24.3 on Debian Sid also crashes. I get a "Fatal error 6: Aborted", Emacs 24.4 (bleeding edge) survives this scan just fine. Ultimately this |
Thank you for taking the time to look into this. I'm glad I'm not alone! I guess the next step is to find out what input is tripping up emacs and work out a way to reproduce this bug without nmap. I'll be looking forward to 24.4. |
i can reproduce this with locally compiled 24.3.1 on 64-bit Debian Wheezy, using locally compiled A backtrace, fwiw:
|
i have a tcpdump capture file of the packets exchanged in the leadup to the crash; might that be of use? |
As an Nmap developer, I can pretty much guarantee that it's the service version detection engine that is causing the crash. To isolate the problem, try these commands:
Please post the name of the service probe ("Service scan sending probe XXX") or the content of the script packet so that we can perhaps modify it to crash fewer services. Thanks! |
Thanks for your help! The first command is enough to cause the crash:
|
@flexibeast Here's the probe that is sent:
You should be able to reproduce with this one-liner:
|
@bonsaiviking Yep, that one-liner reproduced the crash for me! Thanks for your help with this. :-) |
For some reason, nmap -A is crashing emacs consistently when simple-httpd is running.
nmap 6.46 and emacs 24.3.1 on OSX, built with homebrew:
Steps to reproduce:
Emacs crashes every time. nmap without -A is completely fine though. nmap -A is a more thorough scan that does OS, version and script detection.
I have absolutely no idea what's going on - if it's unique to my computer, OSX or emacs in general. I'm going to look into it and update this issue if I find anything!
The text was updated successfully, but these errors were encountered: