public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "rmoseley at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4157] debug crashs with infinite null pointer exceptions
Date: Wed, 07 Mar 2007 13:20:00 -0000	[thread overview]
Message-ID: <20070307132001.11927.qmail@sourceware.org> (raw)
In-Reply-To: <20070306214739.4157.cagney@redhat.com>


------- Additional Comments From rmoseley at redhat dot com  2007-03-07 13:20 -------
I cannot duplicate this problem on my FC5/x86 machine running the latest
software/kernel(2.6.19-1.2288.2.4.fc5) nor can I duplicate it on my FC6/AMD 64
machine running the latest software/kernel(2.6.19-1.2911.6.4.fc6).  *Almost* the
proper thing occurs, the source window remains empty until I click on on a frame
and then the assembly code appears in the window.

This appears to be very similar to but not exactly like bz# 4093
(http://sourceware.org/bugzilla/show_bug.cgi?id=4093) which I fixed last week.  

Make sure the most current cdtparser.jar compiled with the change I committed on
Feb 27 is being used.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|frysk-bugzilla at sourceware|rmoseley at redhat dot com
                   |dot org                     |
             Status|NEW                         |ASSIGNED


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

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


      reply	other threads:[~2007-03-07 13:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 21:47 [Bug general/4157] New: " cagney at redhat dot com
2007-03-07 13:20 ` rmoseley at redhat dot com [this message]

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=20070307132001.11927.qmail@sourceware.org \
    --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).