public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4847] New: testSteppingtestHitAndRun(frysk.proc.TestBreakpoints)java.lang.NullPointerException
Date: Thu, 26 Jul 2007 15:29:00 -0000	[thread overview]
Message-ID: <20070726152821.4847.mark@klomp.org> (raw)

Since kernel 2.6.22.1-27.fc7 (x86 SMP) this test fails because the abort(),
which should never be reached is triggered in funit-breakpoints:

  // Generating a trap event ourselves, simulating "bad code".  Setup
  // a sigsetjump so we can handle it and return from this function
  // safely when the signal handler uses longjmp. On some
  // architectures the PC isn't incremented on invallid/trapping
  // instructions. So this makes sure we skip it when we return.
  if (sigsetjmp (env, 1) == 0)
    {
      send_trap++;
#if defined(__i386__) || defined(__x86_64__)
      asm("int3");
#elif defined(__powerpc64__) || defined(__powerpc__)
      asm(".long 0x7d821008");
#else
      #error unsuported architecture
#endif
      abort(); // Should never be reached.

This is most likely related to and depends on a real fix for handling signals
during stepping outlined in bug #4747 (int3 is a somewhat difficult case though,
that probably should be handled independently by special casing since it
generates a SIGTRAP which isn't a rt signal, so it doesn't queue multiple and
you will only get one).

1)
testSteppingtestHitAndRun(frysk.proc.TestBreakpoints)java.lang.NullPointerException
   at java.lang.Integer.parseInt(libgcj.so.8rh)
   at java.lang.Integer.decode(libgcj.so.8rh)
   at frysk.proc.TestBreakpoints$GoAround.run(TestRunner)
2)
testSteppingtestInsertRemove(frysk.proc.TestBreakpoints)java.lang.NullPointerException
   at java.lang.Integer.parseInt(libgcj.so.8rh)
   at java.lang.Integer.decode(libgcj.so.8rh)
   at frysk.proc.TestBreakpoints$GoAround.run(TestRunner)
3) testSteppingAddLots(frysk.proc.TestBreakpoints)java.lang.NullPointerException
   at java.lang.Integer.parseInt(libgcj.so.8rh)
   at java.lang.Integer.decode(libgcj.so.8rh)
   at frysk.proc.TestBreakpoints$GoAround.run(TestRunner)

-- 
           Summary: testSteppingtestHitAndRun(frysk.proc.TestBreakpoints)jav
                    a.lang.NullPointerException
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: mark at klomp dot org
 BugsThisDependsOn: 4747


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

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


             reply	other threads:[~2007-07-26 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 15:29 mark at klomp dot org [this message]
2007-08-10 11:21 ` [Bug general/4847] testSteppingtestHitAndRun(frysk.proc.TestBreakpoints)java.lang.NullPointerException mark at klomp dot org
2007-08-15 11:07 ` mark at klomp dot org
2008-04-17 16:36 ` mark at klomp dot org

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=20070726152821.4847.mark@klomp.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).