search

juancarmena / xuggle

Automatically exported from code.google.com/p/xuggle
0 stars 0 forks source link

Native Crash while running run-tests-java #17

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
copied from:
https://sourceforge.net/tracker2/?func=detail&aid=2510128&group_id=248424&atid=1
126411

Original issue reported on code.google.com by tre...@gmail.com on 17 Jan 2009 at 12:25

GoogleCodeExporter commented 8 years ago 
Okay, back for more.
While i'm running memtest on my main computer to check for a bad memory module i
created a xuggler build setup on my laptop, which passed the native tests, so 
i'm
putting the segmentation fault to some hardware and/or software problem in my 
main
computer.

Okay, as that issue is cleared i'm back to the reason i've opened the tracker 
item at
sf, i'm still getting a Native Crash while running the java tests (and now on a
different machine, though i'm still using the mingw and msys zips art provided,
re-downloaded them).

    [junit] Running com.xuggle.xuggler.UtilsTest
    [junit] Execution protection violation
    [junit] #
    [junit] # An unexpected error has been detected by Java Runtime Environment:
    [junit] #
    [junit] #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6ada3918, pid=103    
                                        6, tid=2716
    [junit] #
    [junit] # Java VM: Java HotSpot(TM) Client VM (11.0-b15 mixed mode, sharing     
                                        windows-x86)
    [junit] # Problematic frame:
    [junit] # C  0x6ada3918
    [junit] #
    [junit] # An error report file with more information is saved as:
    [junit] # c:\xuggle-xuggler\build\test\output\hs_err_pid1036.log
    [junit] #
    [junit] # If you would like to submit a bug report, please visit:
    [junit] #   http://java.sun.com/webapps/bugreport/crash.jsp
    [junit] # The crash happened outside the Java Virtual Machine in native code    
                                        .
    [junit] # See problematic frame for where to report the bug.
    [junit] #
    [junit] Running com.xuggle.xuggler.UtilsTest
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec

BUILD FAILED
c:\xuggle-xuggler\mk\buildtools\buildhelper.xml:619: Test 
com.xuggle.xuggler.Uti    
                                   lsTest failed (crashed)

I've submitted both crash logs (same issue, different runs) and the contents of 
the
output folder.

So while this is still a "works for me" situation, i'm still unable to compile 
on
windows.

Is there someway to force the java tests to run against the RC3 stuff instead 
of the
stuff i compiled?

Original comment by alka.set...@gmail.com on 22 Jan 2009 at 6:02

Attachments:

GoogleCodeExporter commented 8 years ago 
Hi farenheit,

Unfortunately no; the run-tests can't be done with the windows installer.  
Also, the
"memcheck" targets don't do anything extra on Windows; they only work on Linux.

Sounds like the RC3 installer is working for you (yes)?  But I'd still like to 
know
where the pain is coming from.

You can find the RC3 source code in the RC3 SVN branch:
http://xuggle.googlecode.com/svn/branches/xuggler-1.17.RC3/

Can you upload the EXACT version numbers you use for each of these:
gcc --version
g++ --version
make --version
perl -version
java -version
javac -version
ant -version
%JAVA_HOME%
%XUGGLE_HOME%

Original comment by art.cla...@gmail.com on 22 Jan 2009 at 6:17

GoogleCodeExporter commented 8 years ago 
Good? news.  I've got an XP server up and running now, and when I compile on 
it, the
Utils Test crashes (although with a different trace than what you have).

When I compile on Vista, no such problem.  I'm reopening for now.

Original comment by art.cla...@gmail.com on 25 Jan 2009 at 8:26

GoogleCodeExporter commented 8 years ago 
we have a potential fix and are testing it now.  hopefully we'll patch the tip 
of
tree by end of day.

but if you're curious, looks like you'll need Microsoft's VC++ to build.  We 
tested
on VC 2005 (since it's the older version) specifically for the "lib" tool.

You can get the free version here:
http://www.microsoft.com/express/download/

To build on windows you need to make sure that the "vcvars32.bat" file is 
executed
first and all environment variables it requires are in your shell.

Original comment by art.cla...@gmail.com on 26 Jan 2009 at 11:00

GoogleCodeExporter commented 8 years ago

Original comment by art.cla...@gmail.com on 26 Jan 2009 at 11:06

GoogleCodeExporter commented 8 years ago 
Sorry, for some reason this is not sending replies to my mail. Which is why i 
haven't said anything in the meantime (even though i was testing stuff).

So, from the top, yes, RC3 works as expected, as for the other stuff you 
requested:

$ gcc/g++ -v       
Using built-in specs.
Target: mingw32
Configured with: ../gcc-4.2.4/configure --prefix=/mingw --host=mingw32 --
target=mingw32 --build=mingw32 
--enable-languages=c,ada,c++,fortran,objc,obj-c++ --
disable-nls --disable-win32-registry --enable-libgomp --disable-werror --enable-
threads --disable-symvers --enable-cxx-flags=-fno-function-sections -fno-data-
sections --enable-fully-dynamic-string --enable-sjlj-exceptions
Thread model: win32
gcc version 4.2.4 (TDM-1 for MinGW)

$ make --version
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for i686-pc-msys

$ perl -version

This is perl, v5.10.0 built for MSWin32-x86-multi-thread
(with 5 registered patches, see perl -V for more detail)

Copyright 1987-2007, Larry Wall

Binary build 1004 [287188] provided by ActiveState http://www.ActiveState.com
Built Sep  3 2008 13:16:37

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

$ java -version
java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) Client VM (build 11.0-b16, mixed mode, sharing)

$ javac -version
javac 1.6.0_11

$ ant -version
Apache Ant version 1.7.1 compiled on June 27 2008

echo %JAVA_HOME%
C:\Programas\Java\jdk

echo %XUGGLE_HOME%
C:\stage

Also, about the VC++ lib tool, i've download the express version (vc2008 c++) 
and 
i'm currently looking to see if i can get this work :P

Original comment by alka.set...@gmail.com on 28 Jan 2009 at 6:58

GoogleCodeExporter commented 8 years ago 
Great!  Thanks.

By the way for the LIB tool to work you'll need the latest tip of tree source 
(not
RC3 source).

We have a continuous XP build server testing this, and for the last 20 checkins
everything's been good.

Original comment by art.cla...@gmail.com on 28 Jan 2009 at 7:03

GoogleCodeExporter commented 8 years ago 
Hi again, okay figured out i had to star this bug report to get mails :P

Okay, the good news is that i've managed to complete a build run, the bad news 
is 
that it took me two tries, the first one failed at:

[junit] Running com.xuggle.xuggler.AudioSamplesTest

with a Native Crash but the second run went okay (stupidly i forgot to save the 
crash log before starting a new run, that's why there's no crash log)

Btw, good job on reducing the number of external jars needed to use xuggler :)

I'll now run everything a third time, if it fails again i'll post back, 
otherwise 
thumbs up :)

Original comment by alka.set...@gmail.com on 28 Jan 2009 at 8:16