Closed GoogleCodeExporter closed 8 years ago
As you can see above there are no 'Network-Clients'
listed on bt4??? how do i fix this? thank you
Original comment by mannydia...@gmail.com
on 30 Mar 2011 at 4:30
Are you getting a core file with the segmentation fault? If so, it will be
easier to debug the core file if you perform this command first:
ulimit -unlimited
...and then re-run the scenario the produces the seg-fault. I have seen
segmentation faults for a long time on my box, and this helps a bit in
debugging them. The code owner, Lukas, may be able to find the problem faster,
if he has time to look into it.
Original comment by cpmitc...@gmail.com
on 30 Mar 2011 at 4:31
Typo! Try this command:
ulimit -c unlimited
Original comment by cpmitc...@gmail.com
on 30 Mar 2011 at 7:09
do i run it as
pyrit unlimit -c unlimited
?? because i couldnt get it to work
Original comment by mannydia...@gmail.com
on 31 Mar 2011 at 4:59
No, just run this command first before running pyrit:
ulimit -c unlimited
Next, run your pyrit commands from the same terminal.
Original comment by cpmitc...@gmail.com
on 1 Apr 2011 at 6:31
i run ulimit -c unlimited than i run it and get
Segmentation fault (core dumped) PMKs per second.
and i run it with another file and get
Exception in thread Thread-2:9583 PMKs per second.
Traceback (most recent call last):
File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
self.run()
File "/usr/lib/python2.5/site-packages/cpyrit/pckttools.py", line 709, in run
solution = self.solve(results)
ValueError: All PMKs must be strings of 32 characters
Segmentation fault (core dumped)6 PMKs per second.
and i got this file on my desktop that says core.... type program crash data
Original comment by mannydia...@gmail.com
on 17 Apr 2011 at 8:13
I highly suspect that you suffer from random memory corruption. The error
"ValueError: All PMKs must be strings of 32 characters" that you see is just a
safeguard and should never be triggered.
Please also see https://code.google.com/p/pyrit/issues/detail?id=266
Original comment by lukas.l...@gmail.com
on 28 Apr 2011 at 9:21
Original issue reported on code.google.com by
mannydia...@gmail.com
on 30 Mar 2011 at 6:06