Closed p5pRT closed 19 years ago
I recently "upgraded" gcc from 3.3 to 3.3.2 - now DB_File does not work.
5 tests fail in the test suite - all involving DB_File ext/DB_File/t/db-btree.t ext/DB_File/t/db-hash.t ext/DB_File/t/db-recno.t lib/Memoize/t/errors.t lib/Memoize/t/tie.t
More simply: % ./perl -Ilib -MDB_File -e1 Segmentation fault
perl-5.8.6 compiled and passed all tests with gcc 3.3
I recently "upgraded" gcc from 3.3 to 3.3.2 - now DB_File does not work.
5 tests fail in the test suite - all involving DB_File ext/DB_File/t/db-btree.t ext/DB_File/t/db-hash.t ext/DB_File/t/db-recno.t lib/Memoize/t/errors.t lib/Memoize/t/tie.t
More simply: % ./perl -Ilib -MDB_File -e1 Segmentation fault
perl-5.8.6 compiled and passed all tests with gcc 3.3
Paul Cc: porters
I tried compiling db-3.1.17 with gcc-3.4.3 and then compiling perl-5.8.6 with the same gcc. I had problems getting the perl configuration/compilation to see and link to the db library\, and then\, when I did\, I got a segmentation fault with the same (or similar) back trace.
I then tried to build another XS extension and had more linking problems.
My conclusion is that the fault is with my build of gcc-3.4.3 not with db or DB_File.
I have given up and reinstalled gcc-3.3 and am rebuilding perl-5.8.6 with that. So it will be difficult for me to do further investigation of gcc-3.3.2+ or -3.4+
Robin
-----Original Message----- From: Paul Marquess [mailto:paul.marquess@ntlworld.com] Sent: 01 February 2005 17:39 To: 'Robin Barker' Subject: RE: [perl #33054] Segmentation fault in DB_File with perl-5.8.6 gcc-3.3.2
Hmmm\, not sure about mixing'n'matching gcc. Any chance you could try building both with the same gcc?
Paul
-----Original Message----- From: Robin Barker [mailto:Robin.Barker@npl.co.uk] Sent: 01 February 2005 17:33 To: 'paul.marquess@ntlworld.com' Subject: RE: [perl #33054] Segmentation fault in DB_File with perl-5.8.6 gcc-3.3.2
Paul
I've been building perl with 64-bit and db since I first compiled db- 3.1.17 (in 2000).
I successfully built perl-5.8.6 with 64-bit and db-3.1.17 using gcc-3.3 I successfully built perl-5.8.6 with 64-bit and db-4.3.27 using gcc-3.4.3
So I guess there is some incompatibility between the perl build using newer gcc and db built with an older gcc.
Robin
------------------------------------------------------------------- This e-mail and any attachments may contain confidential and/or privileged material; it is for the intended addressee(s) only. If you are not a named addressee\, you must not use\, retain or disclose such information.
NPL Management Ltd cannot guarantee that the e-mail or any attachments are free from viruses.
NPL Management Ltd. Registered in England and Wales. No: 2937881 Registered Office: Teddington\, Middlesex\, United Kingdom TW11 0LW. -------------------------------------------------------------------
This e-mail and any attachments may contain confidential and/or privileged material; it is for the intended addressee(s) only. If you are not a named addressee\, you must not use\, retain or disclose such information.
NPL Management Ltd cannot guarantee that the e-mail or any attachments are free from viruses.
NPL Management Ltd. Registered in England and Wales. No: 2937881 Registered Office: Teddington\, Middlesex\, United Kingdom TW11 0LW.
[Robin.Barker@npl.co.uk - Thu Feb 03 06:21:49 2005]:
Paul Cc: porters
I tried compiling db-3.1.17 with gcc-3.4.3 and then compiling perl- 5.8.6 with the same gcc. I had problems getting the perl configuration/compilation to see and link to the db library\, and then\, when I did\, I got a segmentation fault with the same (or similar) back trace.
I then tried to build another XS extension and had more linking problems.
My conclusion is that the fault is with my build of gcc-3.4.3 not with db or DB_File.
I have given up and reinstalled gcc-3.3 and am rebuilding perl-5.8.6 with that. So it will be difficult for me to do further investigation of gcc- 3.3.2+ or -3.4+
Robin
-----Original Message----- From: Paul Marquess [mailto:paul.marquess@ntlworld.com] Sent: 01 February 2005 17:39 To: 'Robin Barker' Subject: RE: [perl #33054] Segmentation fault in DB_File with perl- 5.8.6 gcc-3.3.2
Hmmm\, not sure about mixing'n'matching gcc. Any chance you could try building both with the same gcc?
Paul
-----Original Message----- From: Robin Barker [mailto:Robin.Barker@npl.co.uk] Sent: 01 February 2005 17:33 To: 'paul.marquess@ntlworld.com' Subject: RE: [perl #33054] Segmentation fault in DB_File with perl- 5.8.6 gcc-3.3.2
Paul
I've been building perl with 64-bit and db since I first compiled db- 3.1.17 (in 2000).
I successfully built perl-5.8.6 with 64-bit and db-3.1.17 using gcc- 3.3 I successfully built perl-5.8.6 with 64-bit and db-4.3.27 using gcc- 3.4.3
So I guess there is some incompatibility between the perl build using newer gcc and db built with an older gcc.
I'm running against a current blead on OpenBSD compiled with gcc-2.9.5 and I SEGFAULT as well. The e>rror I get is:
perl -Ilib -MDB_File -e1 perl:/home/steve/perl-current/lib/auto/Fcntl/Fcntl.so: undefined symbol 'Perl_Tstack_sp_ptr' lazy binding failed! Segmentation fault (core dumped)
The RT System itself - Status changed from 'new' to 'open'
I'm running against a current blead on OpenBSD compiled with gcc-2.9.5 and I SEGFAULT as well. The e>rror I get is:
perl -Ilib -MDB_File -e1 perl:/home/steve/perl-current/lib/auto/Fcntl/Fcntl.so: undefined symbol 'Perl_Tstack_sp_ptr' lazy binding failed! Segmentation fault (core dumped)
...but it is fixed on OpenBSD 3.7. Ticket resolved.
@smpeters - Status changed from 'open' to 'resolved'
Migrated from rt.perl.org#33054 (status was 'resolved')
Searchable as RT33054$