public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "mcvet at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/3728] New: Stepping johntheripper destroys stack trace
Date: Thu, 14 Dec 2006 20:01:00 -0000	[thread overview]
Message-ID: <20061214200123.3728.mcvet@redhat.com> (raw)

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.

-- 
           Summary: Stepping johntheripper destroys stack trace
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: mcvet at redhat dot com
                CC: cagney at redhat dot com,jan dot kratochvil at redhat
                    dot com,mcvet at redhat dot com
OtherBugsDependingO 1633,2936,3076
             nThis:


http://sourceware.org/bugzilla/show_bug.cgi?id=3728

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


             reply	other threads:[~2006-12-14 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14 20:01 mcvet at redhat dot com [this message]
2006-12-14 20:02 ` [Bug general/3728] " mcvet at redhat dot com
2007-01-04 18:12 ` mcvet at redhat dot com
2007-01-12 11:18 ` jan dot kratochvil at redhat dot com
2007-01-24 20:36 ` jan dot kratochvil at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061214200123.3728.mcvet@redhat.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).