From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <frysk-bugzilla-return-1064-listarch-frysk-bugzilla=sourceware.org@sourceware.org>
Received: (qmail 22382 invoked by alias); 31 Jan 2007 17:21:09 -0000
Received: (qmail 22252 invoked by uid 48); 31 Jan 2007 17:20:48 -0000
Date: Wed, 31 Jan 2007 17:21:00 -0000
From: "pmuldoon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Message-ID: <20070131172048.3948.pmuldoon@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug general/3948] New: testcase LinuxDeadTask getMemory()
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:frysk-bugzilla-subscribe@sourceware.org>
List-Post: <mailto:frysk-bugzilla@sourceware.org>
List-Help: <mailto:frysk-bugzilla-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: frysk-bugzilla-owner@sourceware.org
X-SW-Source: 2007-q1/txt/msg00212.txt.bz2
List-Id: <frysk-bugzilla.sourceware.org>

When a task.getMemory() occurs on a LinuxDeadTask, the operation will be handled
and redirected to a corefile. This requires a memory offset -> file offset
adjustment as well as dealing with endian/alignment issues.

The operation must be transparent to the abstract class Task.

-- 
           Summary: testcase LinuxDeadTask getMemory()
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: pmuldoon at redhat dot com
OtherBugsDependingO 1595
             nThis:


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

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