Re: Debugging c++ shared libraries

2002-05-21 Thread Bill Moseley
At 09:34 PM 05/21/02 +0100, Nicholas Clark wrote: First, thanks for helping. I really appreciate it. >I think it's good news. It's conclusive proof that the problem is in the >dynamic linking. It's not in your module, the aspell library or core perl. >So at least you know where it is. Ok, wel

Re: Debugging c++ shared libraries

2002-05-21 Thread Nicholas Clark
On Mon, May 20, 2002 at 05:12:24PM -0700, Bill Moseley wrote: > At 10:49 PM 05/20/02 +0100, Nicholas Clark wrote: > >He means run 'make perl' in the extension directory, rather than make > >It builds a new perl statically linked with the extension. > > I'm feeling more clueless. > > So, I built

Re: Debugging c++ shared libraries

2002-05-21 Thread Nick Ing-Simmons
Bill Moseley <[EMAIL PROTECTED]> writes: >At 10:03 PM 05/20/02 +0100, Nick Ing-Simmons wrote: >>It works on linux/solaris and probably elsewhere with modern C++ >>systems. > >What "it" are you referring to? My module? Yes. > >>Anything which mixes C++, exceptions and dynamic loading is not >>

Re: Debugging c++ shared libraries

2002-05-20 Thread Bill Moseley
At 10:49 PM 05/20/02 +0100, Nicholas Clark wrote: >He means run 'make perl' in the extension directory, rather than make >It builds a new perl statically linked with the extension. I'm feeling more clueless. So, I built perl 5.7.3 once again (I forgot and used -Duseshrplib the first time...) An

Re: Debugging c++ shared libraries

2002-05-20 Thread Nicholas Clark
On Mon, May 20, 2002 at 05:30:50PM +0100, Nick Ing-Simmons wrote: > Bill Moseley <[EMAIL PROTECTED]> writes: > BSD may still be using a traditional "a.out" object format which does > not have the hooks (e.g. SunOS also used to fail this sort of thing.) > >On FreeBSD 4.5 with 5.005_03 it always a

Re: Debugging c++ shared libraries

2002-05-20 Thread Nicholas Clark
On Mon, May 20, 2002 at 09:48:35AM -0700, Bill Moseley wrote: > At 05:30 PM 05/20/02 +0100, Nick Ing-Simmons wrote: > >>If I copy the .xs code into a main {} block and build a stand-alone C > >>program it works fine everyplace. > > > >Static linking the extension into perl should also work. > > H

Re: Debugging c++ shared libraries

2002-05-20 Thread Bill Moseley
At 10:03 PM 05/20/02 +0100, Nick Ing-Simmons wrote: >It works on linux/solaris and probably elsewhere with modern C++ >systems. What "it" are you referring to? My module? >Anything which mixes C++, exceptions and dynamic loading is not >going to be as portable as perl (which is just ANSI C).

Re: Debugging c++ shared libraries

2002-05-20 Thread Nick Ing-Simmons
Bill Moseley <[EMAIL PROTECTED]> writes: >At 05:30 PM 05/20/02 +0100, Nick Ing-Simmons wrote: >>>If I copy the .xs code into a main {} block and build a stand-alone C >>>program it works fine everyplace. >> >>Static linking the extension into perl should also work. > >Hum, not exactly sure what yo

Re: Debugging c++ shared libraries

2002-05-20 Thread Bill Moseley
At 05:30 PM 05/20/02 +0100, Nick Ing-Simmons wrote: >>If I copy the .xs code into a main {} block and build a stand-alone C >>program it works fine everyplace. > >Static linking the extension into perl should also work. Hum, not exactly sure what you are suggesting. My work with xs has been ra

Re: Debugging c++ shared libraries

2002-05-20 Thread Nick Ing-Simmons
Bill Moseley <[EMAIL PROTECTED]> writes: >I have a module that is a xs interface to the Aspell/Pspell library. The >library is written in c++. The module is Text::Pspell on CPAN. Whether and how constructors get called for static objects defined in loadables is rather platform dependent. linux