Bug 3728 - Stepping johntheripper destroys stack trace
Summary: Stepping johntheripper destroys stack trace
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on: 3699 3791
Blocks: 1633 2936 3076
  Show dependency tree / graph
 
Reported: 2006-12-14 20:01 UTC by Mike Cvet
Modified: 2007-01-12 15:25 UTC (History)
3 users (show)

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

Attachments
Stepped into this stack trace (70.42 KB, image/png)
2006-12-14 20:02 UTC, Mike Cvet 		Details
View All 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-14 20:01:23 UTC 
Linestepping johntheripper on amd64 (with debuginfo and no optimization) was 
going fine, until the stacktrace started accumulating "null ()" in the top few 
frames of the stacktrace with the rest of the trace intact, and finally 
resulted in a single null (). Line stepping past this point resulted in a full 
stacktrace.

I'll attach a screenshot in a sec.
Comment 1 Mike Cvet 2006-12-14 20:02:29 UTC 
Created attachment 1464 [details]
Stepped into this stack trace