public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: frysk builds cleanly on Fedora 7
Date: Mon, 18 Jun 2007 11:28:00 -0000	[thread overview]
Message-ID: <1182164686.4534.14.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <4672C531.6060405@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2910 bytes --]

Hi,

On Fri, 2007-06-15 at 12:58 -0400, Andrew Cagney wrote:
> Is there a bug for this one?

There is now: http://sourceware.org/bugzilla/show_bug.cgi?id=4653
Most issues were fixed by your latest patch to the common build files.
But some others still remain (see the bug report).

But this wasn't the cause of the many failures on F7. Nurding seems to
have fixed most of those with:

2007-06-15  Nurdin Premji  <npremji@redhat.com>

	* DwarfDieFactory.java (loadDies): Call System.err.println 
	for each class, avoids ecj optimizing out these classes.

Although calling println seems a little yucky. But it did seem to work.

Now Fedora 7 (x86) seems to get somewhat similar results (in frysk-core)
compared to Fedora Core 6 (x86_64) for me. Although there are still some
errors/failures on both:

Fedora Core 6 x86_64:
There was 1 error:
1) testHpdBreakpointInline(frysk.bindir.TestFhd)frysk.expunit.TimeoutException: Timeout of 5 expired
There were 4 failures:
1) testSliceAddressSpace(frysk.proc.ptrace.TestByteBuffer)junit.framework.AssertionFailedError: unexpected signal Sig_IO
2) testAttachToAttachedOtherTask(frysk.proc.TestTaskObserver)junit.framework.AssertionFailedError: event loop run explictly stopped (terminated)
3) testVarOutOfScope(frysk.rt.TestDisplayValue)junit.framework.AssertionFailedError: Variable value at first breakpoint expected:<5> but was:<0>
4) testInstructionNext(frysk.rt.TestSteppingEngine)junit.framework.AssertionFailedError: line number

Fedora 7 x86:
There were 6 errors:
1) testHpdArray(frysk.bindir.TestFhd)frysk.expunit.TimeoutException: Timeout of 5 expired
2) testHpdBreakpointInline(frysk.bindir.TestFhd)frysk.expunit.TimeoutException: Timeout of 5 expired
3) testSyscallRunning(frysk.proc.TestSyscallRunning)java.lang.NullPointerException
4) testLinuxPPC(frysk.proc.TestSyscallsWithAudit)java.lang.ArrayIndexOutOfBoundsException: 302
5) testLinuxPPC64(frysk.proc.TestSyscallsWithAudit)java.lang.ArrayIndexOutOfBoundsException: 302
6) testVarOutOfScope(frysk.rt.TestDisplayValue)java.lang.ArrayIndexOutOfBoundsException: 33
There were 4 failures:
1) testAttachToAttachedOtherTask(frysk.proc.TestTaskObserver)junit.framework.AssertionFailedError: event loop run explictly stopped (terminated)
2) testTerminateKillKILL(frysk.proc.TestTaskTerminateObserver)junit.framework.AssertionFailedError: terminating value expected:<-9> but was:<128>
3) testTerminatingKillKILL(frysk.proc.TestTaskTerminateObserver)junit.framework.AssertionFailedError: terminating value expected:<-9> but was:<128>
4) testStepOver(frysk.rt.TestSteppingEngine)junit.framework.AssertionFailedError: line number

Interestingly it seems there are some new ppc syscalls we don't
recognize according to libaudit on Fedora 7. Filed that as bug
http://sourceware.org/bugzilla/show_bug.cgi?id=4658
Anyone any ideas about the others?

Cheers,

Mark

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-06-18 11:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13 13:20 Andrew Cagney
2007-06-13 14:18 ` Elena Zannoni
2007-06-13 21:55   ` Kris Van Hees
2007-06-14 13:45   ` Mark Wielaard
2007-06-15 13:55     ` Mark Wielaard
2007-06-15 17:29       ` Andrew Cagney
2007-06-18 11:28         ` Mark Wielaard [this message]
2007-06-14  9:36 ` Mark Wielaard
2007-06-14  9:57   ` Mark Wielaard
2007-06-14 14:24     ` Andrew Cagney

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=1182164686.4534.14.camel@dijkstra.wildebeest.org \
    --to=mark@klomp.org \
    --cc=cagney@redhat.com \
    --cc=frysk@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).