bugGNU Octave - Bugs: bug #37205, running JIT tests with valgrind:...

 
 

bug #37205: running JIT tests with valgrind: possible memory issues and segfault

Submitted by:  John W. Eaton <jwe>
Submitted on:  Mon Aug 27 13:41:55 2012  
 
Category: InterpreterSeverity: 3 - Normal
Priority: 1 - LaterItem Group: Crash
Status: FixedAssigned to: None
Originator Name: Open/Closed: Closed
Release: devOperating System: GNU/Linux

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Mon Feb 2 04:36:12 2015, comment #7:

Somewhere in the space of a year and a half this seems to have fixed itself. I no longer get a segfault when running JIT under valgrind. Closing report.

Rik <rik5>
Project Administrator
Thu Oct 10 22:04:57 2013, comment #6:

This issue is still with us (10/10/13). Again, it seems to exist only in the valgrind environment so perhaps this isn't desperate to fix.

I can run Octave, but when I try to run the jit.tst file I get a segmentation fault.

Rik <rik5>
Project Administrator
Thu Mar 14 21:53:05 2013, comment #5:

I compiled recently and I have a few more datapoints. The tests pass if JIT is disabled in configure. They also pass if Java is disabled. So it appears that JIT and Java may be competing over the CPU flags. Or maybe they only compete when valgrind is also in the mix.

I'm at revision 16303:085976d9ef08 which is after Mike's cset that restores the Floating Point flags after every Java call. It may be that more flags, such as the SSE-associated stuff, needs to be restored.

Rik <rik5>
Project Administrator
Mon Aug 27 18:00:54 2012, comment #4:

As another datapoint, I do not compile with LLVM because my version is too old, and I can run the test suite under valgrind. This sure looks like a problem in pt-jit.cc.

Rik <rik5>
Project Administrator
Mon Aug 27 16:18:04 2012, comment #3:

Right, I use tcsh and setenv...
works.

Thanks

Michael Godfrey <godfrey>
Mon Aug 27 16:13:09 2012, comment #2:

That's Bourne shell syntax, so it should work in bash.

Do you use a C-shell derivative? If so, then you'd need to write something like

Or, is the missing command valgrind itself? Do you have that installed on your system?

John W. Eaton <jwe>
Project Administrator
Mon Aug 27 15:38:14 2012, comment #1:

John,

I tried the command below, but got
"command not found"

What shell or other trick is needed?

Michael Godfrey <godfrey>
Mon Aug 27 13:41:55 2012, original submission:

Running

failed with

This crash doesn't happen when running the tests without valgrind.

Full log is attached.

John W. Eaton <jwe>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

Attached Files
file #26432:  make-check-log added by jwe (21kB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by rik5 (Posted a comment)
  • -unavailable- added by godfrey (Posted a comment)
  • -unavailable- added by jwe (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 5 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Mon Feb 2 04:36:12 2015rik5Priority5 - Normal=>1 - Later
      StatusNone=>Fixed
      Open/ClosedOpen=>Closed
    Tue Oct 29 17:57:58 2013rik5Summaryrunning tests with valgrind: possible memory issues and segfault=>running JIT tests with valgrind: possible memory issues and segfault
    Mon Aug 27 13:41:55 2012jweAttached File-=>Added make-check-log, #26432

    Back to the top


    Powered by Savane 3.1-cleanup