Bug 3649 - Strange backtracing for johntheripper
Summary: Strange backtracing for johntheripper
Status: ASSIGNED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks: 1633 2936 3076
  Show dependency tree / graph
 
Reported: 2006-12-04 23:08 UTC by Mike Cvet
Modified: 2007-02-22 15:27 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Cvet 2006-12-04 23:08:14 UTC 
On i386 I get a raised SourceWindow saying "no debuginfo" and the 
stacktrace:

# 1 error ()
# 2 null ()
# 3 null ()

On i386, with debuginfo and with -fasynchronous-unwind-tables appended to the 
makefile, I can get this from gdb:

(gdb) bt
#0  0x0806bf44 in MD5_body ()
#1  0x080787f5 in PADDING ()
#2  0x080b0580 in current_salt ()
#3  0xbfff0668 in ?? ()
#4  0x0804d7da in MD5_std_crypt () at MD5_std.c:549
Previous frame inner to this frame (corrupt stack?)



However, on x86_64, I get this through fstack:

Task #9844
#0 0x407859 in MD5_body (): line #728
#1 0x406e0e in MD5_std_crypt (): line #546
#2 0x416491 in crk_password_loop (): line #183
#3 0x41664f in crk_salt_loop (): line #221
#4 0x4166f9 in crk_process_key (): line #239
#5 0x4231c7 in do_wordlist_crack (): line #217
#6 0x419a6e in john_run (): line #276
#7 0x419c03 in main (): line #345
#8 0x2aaaaace3a44 in __libc_start_main ()
#9 0x4017e9 in _start ()