http403 / pyrit

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

Import password issue #71

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
To reproduce the problem
1) try to use import_passwords switch
2) use relatively big dictionary (~ 100 MB)

There are the following errors:

---------------------------------------------------------------
[root@localhost ~]# pyrit -i /tmp/dict.txt  import_passwords
Pyrit 0.2.5-dev (svn r191) (C) 2008, 2009 Lukas Lueg
http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3

Connecting to storage... connected

5000000 lines read. Segmentation fault
---------------------------------------------------------------

or:

---------------------------------------------------------------
[root@localhost home]#
[root@localhost ~]# pyrit -i /tmp/dict.txt  import_passwords
Pyrit 0.2.5-dev (svn r191) (C) 2008, 2009 Lukas Lueg
http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3

Connecting to storage... connected

5000000 lines read. Fatal Python error: Inconsistent interned string state.
Aborted
---------------------------------------------------------------

In the log I can see the following problem:
pyrit[3394] general protection ip:3646c754111 sp:7fff73f3bb7 error:0 in
libpython2.5.so.1.0

My system is Fedora Core 10, 64 bit. Newest pyrit r191. I didn't have this
problem in previous release.

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by lamper...@gmail.com on 19 Nov 2009 at 12:06

GoogleCodeExporter commented 9 years ago
Could you provide a Core-dump of a segmentation-fault ?

Original comment by lukas.l...@gmail.com on 19 Nov 2009 at 4:29

GoogleCodeExporter commented 9 years ago
It seems that one of my RAM card has a defect. I'm running memtests at the 
monent and
it's likely that this was causing the trouble. Sorry for bothering, I'll 
confirm it
tomorrow or on Monday.

Original comment by lamper...@gmail.com on 19 Nov 2009 at 11:42

GoogleCodeExporter commented 9 years ago
RAM defect confirmed. Please remove this issue. Thanx

Original comment by lamper...@gmail.com on 23 Nov 2009 at 9:44

GoogleCodeExporter commented 9 years ago
kk

Original comment by lukas.l...@gmail.com on 23 Nov 2009 at 10:32