Thread: [Paracomp-users] Paracomp crash when compiled in release mode
Brought to you by:
shreekumar
Menu
▾
▴
paracomp-users
|
From: Shree K. <shr...@hp...> - 2008-04-10 16:15:09
|
Hi James,
I ran into the same problem which you faced : crash when paracomp is
compiled in release mode.
My system : an x86_64 machine running Fedora Core 8(x86_64). GCC version
4.1.2
Basically, any program using the library crashes, _if_ paracomp was
compiled in release mode. If paracomp is compiled in debug mode
"release=0" things move just fine.
I investigated this a bit, and found that a dlclose() in
loadCompositePlugin() (pcimpl.cpp) is causing the crash.
----------------------------------------------------------
using namespace paracomp;
@@ -236,7 +242,7 @@
// if the init function returns non-zero, then it cannot be used
if(((*initFunc)())!=0)
{
- dlclose(libHandle);
+ //dlclose(libHandle); // commenting this out gets rid of
the crash
return false;
}
----------------------------------------------------------
Seems to be a compiler related issue, since I don't see this on our RHEL
5 based system (running GCC 3.4.6).
James, do you remember what compiler version you saw the issue on ?
For now, I don't have a solution. Commenting out gets rid of the
problem. This will result in a small memory leak, but should be good to
keep people going.
Just something I thought everybody must know before we find a solution
to the problem.
Regards
-- Shree
|
|
From: James S P. <jam...@ma...> - 2008-04-11 15:57:08
|
Hi Shree,
Same as you gcc 4.1.2 and glibc 2.5.
Regards
James
Shree Kumar wrote:
> Hi James,
>
> I ran into the same problem which you faced : crash when paracomp is
> compiled in release mode.
>
> My system : an x86_64 machine running Fedora Core 8(x86_64). GCC version
> 4.1.2
>
> Basically, any program using the library crashes, _if_ paracomp was
> compiled in release mode. If paracomp is compiled in debug mode
> "release=0" things move just fine.
>
> I investigated this a bit, and found that a dlclose() in
> loadCompositePlugin() (pcimpl.cpp) is causing the crash.
>
> ----------------------------------------------------------
> using namespace paracomp;
> @@ -236,7 +242,7 @@
> // if the init function returns non-zero, then it cannot be used
> if(((*initFunc)())!=0)
> {
> - dlclose(libHandle);
> + //dlclose(libHandle); // commenting this out gets rid of
> the crash
> return false;
> }
> ----------------------------------------------------------
>
> Seems to be a compiler related issue, since I don't see this on our RHEL
> 5 based system (running GCC 3.4.6).
>
> James, do you remember what compiler version you saw the issue on ?
>
> For now, I don't have a solution. Commenting out gets rid of the
> problem. This will result in a small memory leak, but should be good to
> keep people going.
>
> Just something I thought everybody must know before we find a solution
> to the problem.
>
> Regards
> -- Shree
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Paracomp-users mailing list
> Par...@li...
> https://lists.sourceforge.net/lists/listinfo/paracomp-users
--
------------------------------------------------------------------------
James S. Perrin
Visualization
Research Computing Services
The University of Manchester
Kilburn Building, Oxford Road
Manchester, M13 9PL
t: +44 (0) 161 275 6945
e: jam...@ma...
w: www.manchester.ac.uk/researchcomputing
------------------------------------------------------------------------
"The test of intellect is the refusal to belabour the obvious"
- Alfred Bester
------------------------------------------------------------------------
|
|
From: Shree K. <shr...@hp...> - 2008-04-29 07:28:04
|
On Fri, 2008-04-11 at 15:22 +0000, James S Perrin wrote: > Hi Shree, > > Same as you gcc 4.1.2 and glibc 2.5. > Good news. I've fixed this just now :-) http://paracomp.svn.sourceforge.net/viewvc/paracomp?view=rev&revision=60 James, do let me know if it works for you. Cheers -- Shree > Shree Kumar wrote: > > Hi James, > > > > I ran into the same problem which you faced : crash when paracomp is > > compiled in release mode. > > > > My system : an x86_64 machine running Fedora Core 8(x86_64). GCC version > > 4.1.2 > > > > Basically, any program using the library crashes, _if_ paracomp was > > compiled in release mode. If paracomp is compiled in debug mode > > "release=0" things move just fine. > > > > I investigated this a bit, and found that a dlclose() in > > loadCompositePlugin() (pcimpl.cpp) is causing the crash. > > > > ---------------------------------------------------------- > > using namespace paracomp; > > @@ -236,7 +242,7 @@ > > // if the init function returns non-zero, then it cannot be used > > if(((*initFunc)())!=0) > > { > > - dlclose(libHandle); > > + //dlclose(libHandle); // commenting this out gets rid of > > the crash > > return false; > > } > > ---------------------------------------------------------- > > > > Seems to be a compiler related issue, since I don't see this on our RHEL > > 5 based system (running GCC 3.4.6). > > > > James, do you remember what compiler version you saw the issue on ? > > > > For now, I don't have a solution. Commenting out gets rid of the > > problem. This will result in a small memory leak, but should be good to > > keep people going. > > > > Just something I thought everybody must know before we find a solution > > to the problem. > > > > Regards > > -- Shree > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > > Don't miss this year's exciting event. There's still time to save $100. > > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > > _______________________________________________ > > Paracomp-users mailing list > > Par...@li... > > https://lists.sourceforge.net/lists/listinfo/paracomp-users > > -- > ------------------------------------------------------------------------ > James S. Perrin > Visualization > > Research Computing Services > The University of Manchester > Kilburn Building, Oxford Road > Manchester, M13 9PL > > t: +44 (0) 161 275 6945 > e: jam...@ma... > w: www.manchester.ac.uk/researchcomputing > ------------------------------------------------------------------------ > "The test of intellect is the refusal to belabour the obvious" > - Alfred Bester > ------------------------------------------------------------------------ |
|
From: James S P. <jam...@ma...> - 2008-04-29 14:11:25
|
Hi Shree, Yes it works fine. Thanks. James Shree Kumar wrote: > On Fri, 2008-04-11 at 15:22 +0000, James S Perrin wrote: >> Hi Shree, >> >> Same as you gcc 4.1.2 and glibc 2.5. >> > > Good news. I've fixed this just now :-) > > http://paracomp.svn.sourceforge.net/viewvc/paracomp?view=rev&revision=60 > > James, do let me know if it works for you. > > Cheers > -- Shree > >> Shree Kumar wrote: >>> Hi James, >>> >>> I ran into the same problem which you faced : crash when paracomp is >>> compiled in release mode. >>> >>> My system : an x86_64 machine running Fedora Core 8(x86_64). GCC version >>> 4.1.2 >>> >>> Basically, any program using the library crashes, _if_ paracomp was >>> compiled in release mode. If paracomp is compiled in debug mode >>> "release=0" things move just fine. >>> >>> I investigated this a bit, and found that a dlclose() in >>> loadCompositePlugin() (pcimpl.cpp) is causing the crash. >>> >>> ---------------------------------------------------------- >>> using namespace paracomp; >>> @@ -236,7 +242,7 @@ >>> // if the init function returns non-zero, then it cannot be used >>> if(((*initFunc)())!=0) >>> { >>> - dlclose(libHandle); >>> + //dlclose(libHandle); // commenting this out gets rid of >>> the crash >>> return false; >>> } >>> ---------------------------------------------------------- >>> >>> Seems to be a compiler related issue, since I don't see this on our RHEL >>> 5 based system (running GCC 3.4.6). >>> >>> James, do you remember what compiler version you saw the issue on ? >>> >>> For now, I don't have a solution. Commenting out gets rid of the >>> problem. This will result in a small memory leak, but should be good to >>> keep people going. >>> >>> Just something I thought everybody must know before we find a solution >>> to the problem. >>> >>> Regards >>> -- Shree >>> >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >>> Don't miss this year's exciting event. There's still time to save $100. >>> Use priority code J8TL2D2. >>> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >>> _______________________________________________ >>> Paracomp-users mailing list >>> Par...@li... >>> https://lists.sourceforge.net/lists/listinfo/paracomp-users >> -- >> ------------------------------------------------------------------------ >> James S. Perrin >> Visualization >> >> Research Computing Services >> The University of Manchester >> Kilburn Building, Oxford Road >> Manchester, M13 9PL >> >> t: +44 (0) 161 275 6945 >> e: jam...@ma... >> w: www.manchester.ac.uk/researchcomputing >> ------------------------------------------------------------------------ >> "The test of intellect is the refusal to belabour the obvious" >> - Alfred Bester >> ------------------------------------------------------------------------ > -- ------------------------------------------------------------------------ James S. Perrin Visualization Research Computing Services The University of Manchester Kilburn Building, Oxford Road Manchester, M13 9PL t: +44 (0) 161 275 6945 e: jam...@ma... w: www.manchester.ac.uk/researchcomputing ------------------------------------------------------------------------ "The test of intellect is the refusal to belabour the obvious" - Alfred Bester ------------------------------------------------------------------------ |
Thanks for helping keep SourceForge clean.
X