Second ctrl+c should force quit the program

[cyb3rjerry]

Describe the bug
CTRL+C once initiates the "smooth" exit correctly. However, pressing it a second time should "force quit" as it currently simply hangs

To Reproduce
Steps to reproduce the behavior:

1. Run any long scan
2. Press CTRL+C twice
3. See error

Expected behavior
Force quit on second CTRL+C

Screenshots

Desktop (please complete the following information):
Linux cyb3rjerry 5.19.0-23-generic 24-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 14 15:39:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

[cyb3rjerry]

Crawling google and trying to leave for example causes this

[edoardottt]

Can you confirm this c547128 is fixing this issue? @cyb3rjerry

[cyb3rjerry]

@edoardottt LGTM however we might also want to halt printing URLs to avoid confusion
Either that or add a sleep before printing the exit message to make sure it gets printed at the bottom

[edoardottt]

Those are the responses to the requests that have been made before pressing CTRL+C and still didn't get a response. Then when they get it, they print them. What about adding os.Stdout = nil? I don't know what could be a working solution..

I can't even reproduce this bug