public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/6570] New: Report lack of a disassembler at run time as UNRESOLVED / UNSUPPORTED Date: Tue, 27 May 2008 16:16:00 -0000 [thread overview] Message-ID: <20080527161618.6570.cagney@redhat.com> (raw) The old lib.opcodes bindings had a way to detect, at runtime, that there wasn't a disassembler. The testsuite used that to skip (mark as unsupported) disassembler tests. The new bindings lack this (they throw an exception which could be caught?). This will let us correctly fix tests such as: public class TestDisassemblerCommand extends TestLib { public void testHpdDisassemble() { if (unsupported("disassembler", true)) return; to instead be: public void testHpdDisassemble() { if (missingDisassembler()) return; Where frysk.junit.TestCase.missingDisassembler(), modeled on missing32and64(), would report UNRESOLVED on IA-32 and x86-64 where there should be a disassembler, but UNSUPPORTED on PPC where the disassembler is simply missing. -- Summary: Report lack of a disassembler at run time as UNRESOLVED / UNSUPPORTED Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: cagney at redhat dot com OtherBugsDependingO 6541 nThis: http://sourceware.org/bugzilla/show_bug.cgi?id=6570 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
reply other threads:[~2008-05-27 16:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080527161618.6570.cagney@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: linkBe 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).