From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6116 invoked by alias); 5 Jan 2007 22:51:45 -0000 Received: (qmail 6087 invoked by uid 48); 5 Jan 2007 22:51:35 -0000 Date: Fri, 05 Jan 2007 22:51:00 -0000 From: "npremji at redhat dot com" To: frysk-bugzilla@sourceware.org Message-ID: <20070105225134.3837.npremji@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/3837] New: During intensive stack tracing frysk hangs at odd times. X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00035.txt.bz2 List-Id: run the following: make -j2 && while ./frysk-core/TestRunner -console frysk=FINEST frysk.util.StressTestFStack.testClone &> stress.log; do echo success; done will eventually give an error that the testcase took too long. However the testcase actually completed everything it was meant to do, it just took a lot longer than it should have. The hangs seem to be at random times such as the following. Which seems to indicate there is a hang between the switch/break statement in StackCallbacks.accessMem. (Long numbers retrieved using System.currentTimeMillis().) 5-Jan-07 5:19:50 PM frysk.rt.StackCallbacks accessMem FINEST: After getInt 1168035590661 5-Jan-07 5:19:53 PM frysk.rt.StackCallbacks accessMem FINE: Libunwind: read value 0x14 1168035593450 5-Jan-07 5:19:53 PM frysk.rt.StackCallbacks accessMem FINE: Libunwind: reading memory at 0x4aad6d70 1168035593450 -- Summary: During intensive stack tracing frysk hangs at odd times. Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: npremji at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=3837 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.