Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
|
From: Peter Vanroose <peter_vanroose@ya...> - 2005-05-20 18:47:47
|
> I'm getting crashes in the deallocation of arrays used in > the vnl_svd_economy class, specifically the > vnl_fortran_copy<real_t> X(M); at line 30 in vnl_svd_economy.txx. Try setting VNL_CONFIG_THREAD_SAFE in vnl_config.h -- Peter. |
|
From: Peter Vanroose <peter_vanroose@ya...> - 2005-05-20 18:47:47
|
> I'm getting crashes in the deallocation of arrays used in > the vnl_svd_economy class, specifically the > vnl_fortran_copy<real_t> X(M); at line 30 in vnl_svd_economy.txx. Try setting VNL_CONFIG_THREAD_SAFE in vnl_config.h -- Peter. |
|
From: Peter Vanroose <peter_vanroose@ya...> - 2005-05-20 22:49:52
|
> I think LINPACK may not be thread-safe. I don't know about thread-safeness of LINPACK (or v3p/netlib in general), but I'm quite sure that in this case it's the thread-unsafeness of vnl_c_vector_alloc(). -- Peter. |
|
From: Phil Parsonage <philparsonage@ho...> - 2005-05-24 13:35:00
|
Firstly, thanks for the replies. Apologies for taking a while to get back to you, I had to park what I was doing for a while. Having gone back and checked, I have #define VNL_CONFIG_THREAD_SAFE 1 in vnl_config.h, and sure enough, I'm using new and delete to allocate and deallocate, yet I'm still getting a crash. Has anyone had any success using the svd objects from within a thread? I'd actually be happier to pre-allocate any data outside of the thread, as I'm doing the same sized calculation many times - perhaps I need to look at an alternative binding to the netlib code? Has anyone thought of doing the same thing? Phil >From: Peter Vanroose <peter_vanroose@...> >Reply-To: p.vanroose@... >To: Ian Scott <ian.m.scott@...>, Phil Parsonage ><philparsonage@...> >CC: vxl-users <vxl-users@...> >Subject: Re: [Vxl-users] Thread Safety of vnl_svd >Date: Sat, 21 May 2005 00:49:40 +0200 (CEST) > > > I think LINPACK may not be thread-safe. > >I don't know about thread-safeness of LINPACK (or v3p/netlib in >general), but I'm quite sure that in this case it's the >thread-unsafeness of vnl_c_vector_alloc(). > > >-- Peter. |
|
From: Phil Parsonage <philparsonage@ho...> - 2005-05-25 09:34:47
|
Thanks for the replies. Having come back to this, I've recompiled all my VXL libraries making sure that flag is defined and it's still somewhat unhappy. I'm definitely using new and delete, rather than the optimised allocs, but there is something funny going on. Has anyone succesfully used this in a thread? I think I'm going to have to "home-brew" a solution, which I'd rather not do. >From: Peter Vanroose <peter_vanroose@...> >Reply-To: p.vanroose@... >To: Ian Scott <ian.m.scott@...>, Phil Parsonage ><philparsonage@...> >CC: vxl-users <vxl-users@...> >Subject: Re: [Vxl-users] Thread Safety of vnl_svd >Date: Sat, 21 May 2005 00:49:40 +0200 (CEST) > > > I think LINPACK may not be thread-safe. > >I don't know about thread-safeness of LINPACK (or v3p/netlib in >general), but I'm quite sure that in this case it's the >thread-unsafeness of vnl_c_vector_alloc(). > > >-- Peter. |
|
From: Andrew Fitzgibbon <awf@ro...> - 2005-05-25 09:51:47
|
It's the SVD itself: dsvdc. It really ought to be easy to switch it to the LAPACK SVD. (I misspoke if I ever said LINPACK). A. > -----Original Message----- > From: vxl-users-admin@... > [mailto:vxl-users-admin@...] On Behalf Of > Phil Parsonage > Sent: 25 May 2005 10:35 > To: vxl-users@... > Subject: Re: [Vxl-users] Thread Safety of vnl_svd > > > Thanks for the replies. Having come back to this, I've > recompiled all my VXL > libraries making sure that flag is defined and it's still > somewhat unhappy. > I'm definitely using new and delete, rather than the > optimised allocs, but > there is something funny going on. > Has anyone succesfully used this in a thread? I think I'm > going to have to > "home-brew" a solution, which I'd rather not do. > > >From: Peter Vanroose <peter_vanroose@...> > >Reply-To: p.vanroose@... > >To: Ian Scott <ian.m.scott@...>, Phil > Parsonage > ><philparsonage@...> > >CC: vxl-users <vxl-users@...> > >Subject: Re: [Vxl-users] Thread Safety of vnl_svd > >Date: Sat, 21 May 2005 00:49:40 +0200 (CEST) > > > > > I think LINPACK may not be thread-safe. > > > >I don't know about thread-safeness of LINPACK (or v3p/netlib in > >general), but I'm quite sure that in this case it's the > >thread-unsafeness of vnl_c_vector_alloc(). > > > > > >-- Peter. > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > Search APIs Find out how you can build Yahoo! directly into your own > Applications - visit > http://developer.yahoo.net/?fr=offad-ysdn->; ostg-q22005 > > _______________________________________________ > > Vxl-users mailing list > Vxl-users@... > https://lists.sourceforge.net/lists/listinfo/vxl-users > |
|
From: Luis Ibanez <luis.ibanez@ki...> - 2005-05-22 02:54:05
|
netlib is certainly not thread-safe.
The translation from FORTRAN to C left plenty of
"static" variables in the functions.
(2124 of them to be precise...)
In ITK we are planning to edit the result of the
fortran-to-C translation in order to remove this
unnecessary statics.
Luis
------------------------------------------------
vxl-users-request@... wrote:
> Send Vxl-users mailing list submissions to
> vxl-users@...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/vxl-users
> or, via email, send a message with subject or body 'help' to
> vxl-users-request@...
>
> You can reach the person managing the list at
> vxl-users-admin@...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Vxl-users digest..."
>
>
> Today's Topics:
>
> 1. Re: Thread Safety of vnl_svd (Peter Vanroose)
> 2. Re: Thread Safety of vnl_svd (Ian Scott)
> 3. Re: Thread Safety of vnl_svd (Peter Vanroose)
>
> --__--__--
>
> Message: 1
> Date: Fri, 20 May 2005 20:47:37 +0200 (CEST)
> From: Peter Vanroose <peter_vanroose@...>
> Reply-To: p.vanroose@...
> Subject: Re: [Vxl-users] Thread Safety of vnl_svd
> To: Phil Parsonage <philparsonage@...>,
> vxl-users@...
>
>
>>I'm getting crashes in the deallocation of arrays used in
>>the vnl_svd_economy class, specifically the
>>vnl_fortran_copy<real_t> X(M); at line 30 in vnl_svd_economy.txx.
>
>
> Try setting VNL_CONFIG_THREAD_SAFE in vnl_config.h
>
>
> -- Peter.
>
>
> --__--__--
>
> Message: 2
> Date: Fri, 20 May 2005 21:26:20 +0100
> From: Ian Scott <ian.m.scott@...>
> To: Phil Parsonage <philparsonage@...>
> CC: vxl-users <vxl-users@...>
> Subject: Re: [Vxl-users] Thread Safety of vnl_svd
>
> Phil Parsonage wrote:
>
>>Hi,
>>I'm trying to use a vnl_svd object in some threaded code. In
>>non-threaded model, everything works OK, but in the threaded version I'm
>>getting crashes in the deallocation of arrays used in the
>>vnl_svd_economy class, specifically the vnl_fortran_copy<real_t> X(M);
>>at line 30 in vnl_svd_economy.txx.
>>
>>I believe I'm in thred-safe allocation mode - is there anything else
>>anyone could suggest or help me to identify what's going on? I'm on
>>MSVC++ 6 (yes, I know version 6, it's a long story!)
>>
>
>
> I haven't looked, so take this as the series of guesses it is. I think
> we might still be using the LINPACK SVD implementation. I think
> LINPACK may not be thread-safe. If this is the case, the solution is
> to import the newer LAPACK version of SVD into v3d/netlib.
>
> Any volunteers?
>
> Ian.
>
>
> --__--__--
>
> Message: 3
> Date: Sat, 21 May 2005 00:49:40 +0200 (CEST)
> From: Peter Vanroose <peter_vanroose@...>
> Reply-To: p.vanroose@...
> Subject: Re: [Vxl-users] Thread Safety of vnl_svd
> To: Ian Scott <ian.m.scott@...>,
> Phil Parsonage <philparsonage@...>
> Cc: vxl-users <vxl-users@...>
>
>>I think LINPACK may not be thread-safe.
>
>
> I don't know about thread-safeness of LINPACK (or v3p/netlib in
> general), but I'm quite sure that in this case it's the
> thread-unsafeness of vnl_c_vector_alloc().
>
>
> -- Peter.
>
>
>
> --__--__--
>
> _______________________________________________
> Vxl-users mailing list
> Vxl-users@...
> https://lists.sourceforge.net/lists/listinfo/vxl-users
>
>
> End of Vxl-users Digest
>
>
|
|
From: Andrew Fitzgibbon <awf@ro...> - 2005-05-23 10:17:38
|
I would definitely recommend moving to LAPACK instead -- less work, and better code. Should be easier to replace the calls to, e.g.\ dsvdc, than to fix all the statics (I'm sure that more than zero of them really do need to be static). A. > -----Original Message----- > From: vxl-users-admin@... > [mailto:vxl-users-admin@...] On Behalf Of > Luis Ibanez > Sent: 22 May 2005 03:54 > To: vxl-users@... > Subject: [Vxl-users] Re: Thread Safety of vnl_svd > > > > netlib is certainly not thread-safe. > > The translation from FORTRAN to C left plenty of > "static" variables in the functions. > (2124 of them to be precise...) > > In ITK we are planning to edit the result of the > fortran-to-C translation in order to remove this > unnecessary statics. > > > > Luis > > > > ------------------------------------------------ > vxl-users-request@... wrote: > > Send Vxl-users mailing list submissions to > > vxl-users@... > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.sourceforge.net/lists/listinfo/vxl-users > > or, via email, send a message with subject or body 'help' to > > vxl-users-request@... > > > > You can reach the person managing the list at > > vxl-users-admin@... > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Vxl-users digest..." > > > > > > Today's Topics: > > > > 1. Re: Thread Safety of vnl_svd (Peter Vanroose) > > 2. Re: Thread Safety of vnl_svd (Ian Scott) > > 3. Re: Thread Safety of vnl_svd (Peter Vanroose) > > > > --__--__-- > > > > Message: 1 > > Date: Fri, 20 May 2005 20:47:37 +0200 (CEST) > > From: Peter Vanroose <peter_vanroose@...> > > Reply-To: p.vanroose@... > > Subject: Re: [Vxl-users] Thread Safety of vnl_svd > > To: Phil Parsonage <philparsonage@...>, > > vxl-users@... > > > > > >>I'm getting crashes in the deallocation of arrays used in > >>the vnl_svd_economy class, specifically the > >>vnl_fortran_copy<real_t> X(M); at line 30 in vnl_svd_economy.txx. > > > > > > Try setting VNL_CONFIG_THREAD_SAFE in vnl_config.h > > > > > > -- Peter. > > > > > > --__--__-- > > > > Message: 2 > > Date: Fri, 20 May 2005 21:26:20 +0100 > > From: Ian Scott <ian.m.scott@...> > > To: Phil Parsonage <philparsonage@...> > > CC: vxl-users <vxl-users@...> > > Subject: Re: [Vxl-users] Thread Safety of vnl_svd > > > > Phil Parsonage wrote: > > > >>Hi, > >>I'm trying to use a vnl_svd object in some threaded code. In > >>non-threaded model, everything works OK, but in the > threaded version I'm > >>getting crashes in the deallocation of arrays used in the > >>vnl_svd_economy class, specifically the > vnl_fortran_copy<real_t> X(M); > >>at line 30 in vnl_svd_economy.txx. > >> > >>I believe I'm in thred-safe allocation mode - is there > anything else > >>anyone could suggest or help me to identify what's going on? I'm on > >>MSVC++ 6 (yes, I know version 6, it's a long story!) > >> > > > > > > I haven't looked, so take this as the series of guesses it > is. I think > > we might still be using the LINPACK SVD implementation. I think > > LINPACK may not be thread-safe. If this is the case, the > solution is > > to import the newer LAPACK version of SVD into v3d/netlib. > > > > Any volunteers? > > > > Ian. > > > > > > --__--__-- > > > > Message: 3 > > Date: Sat, 21 May 2005 00:49:40 +0200 (CEST) > > From: Peter Vanroose <peter_vanroose@...> > > Reply-To: p.vanroose@... > > Subject: Re: [Vxl-users] Thread Safety of vnl_svd > > To: Ian Scott <ian.m.scott@...>, > > Phil Parsonage <philparsonage@...> > > Cc: vxl-users <vxl-users@...> > > > >>I think LINPACK may not be thread-safe. > > > > > > I don't know about thread-safeness of LINPACK (or v3p/netlib in > > general), but I'm quite sure that in this case it's the > > thread-unsafeness of vnl_c_vector_alloc(). > > > > > > -- Peter. > > > > > > > > --__--__-- > > > > _______________________________________________ > > Vxl-users mailing list > > Vxl-users@... > > https://lists.sourceforge.net/lists/listinfo/vxl-users > > > > > > End of Vxl-users Digest > > > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Oracle Space Sweepstakes > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click > _______________________________________________ > Vxl-users mailing list > Vxl-users@... > https://lists.sourceforge.net/lists/listinfo/vxl-users > |