Fuzzing terminate due to unknow stack trace error about feroxbuster

[Sicks3c]

Hello @epi052

Thank you for your fast reply
Yes Indeed I'm using 1.0.0
I'm currently running some fuzzing will see if the same occurs or it fix

I'll update you in an hour

Regards

[epi052]

Good morning!

Thank you for filing this bug report. I pushed an update to address this problem yesterday. Can you try the same scan with feroxbuster version 1.0.1?

You can check the version by running:

./feroxbuster -V
feroxbuster 1.0.1

I strongly suspect you're using version 1.0.0. Can you please confirm?

[Sicks3c]

Looks like the issue is fixed @epi052

I just have a small question
Is there any way to not show the timeout URLs ?

The quiet will suppress the status and everything ...

Regards

[epi052]

great! glad to hear that particular issue is resolved.

your screenshot cuts off the right-most information. Are those all timeouts?

If so, we could make them warnings, then you'd only see them when -v is used.

Would you mind opening a new issue for that, if it sounds like an agreeable solution?

I'm closing this issue, since v1.0.1 already addresses the initial problem.