Обсуждение: 7.1 beta 4 ODBC Connection Problem
Hello,
I have been successfully using 7.0.2 with our application under Redhat 6.0.
I was using the 7.0.2 RPMs that come with RedHat 6.2.
I decided to test the 7.1 beta 4 with our application, and installed the
RPMs from the PostgreSQL.org ftp site. I was able to install everything, create
our database and check it with psql, however, when I try and access the database
via ODBC, I run into problems.
I get a seg fault when I try and connect to the database via SQLConnect. Below
is a stack trace from teh core file. The crash occurs in sprintf. I'm unsure
if there are perhaps some incompatibilities between my environment and the RPMs
installed, or if this is a bug in the 7.1beta4 code. Does anyone have
any ideas?
Thanks,
Steve
[mergeark@steveark mergeark]$ gdb adopt_std core
GNU gdb 4.17.0.11 with Linux support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
Core was generated by `adopt_std /dev/scd0 1'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /home/mergeark/exe/lib/libmergebox.so...done.
Reading symbols from /usr/lib/libpsqlodbc.so.0...done.
Reading symbols from /home/mergeark/exe/lib/mc3adv.so...done.
Reading symbols from /lib/libm.so.6...done.
Reading symbols from /lib/libdl.so.2...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
Reading symbols from /lib/libnss_files.so.2...done.
#0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 "%c.%c", ap=0xbfffd8ac) at vfprintf.c:1248
vfprintf.c:1248: No such file or directory.
(gdb) bt
#0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 "%c.%c", ap=0xbfffd8ac) at vfprintf.c:1248
#1 0x4017e0b3 in _IO_vsprintf (string=0x400643df "0.0", format=0x40064409 "%c.%c", args=0xbfffd8a8) at iovsprintf.c:47
#2 0x4017876f in sprintf (s=0x400643df "0.0", format=0x40064409 "%c.%c") at sprintf.c:38
#3 0x4004f268 in CC_lookup_pg_version ()
#4 0x4004def9 in CC_connect ()
#5 0x4004d0b4 in SQLConnect ()
#6 0x8057efa in DatabaseConnect ()
#7 0x8057c1e in ADB_DatabaseInit ()
#8 0x804a802 in Initialize_Process () at adopt_std.c:238
#9 0x804bf7b in main (ac=3, av=0xbffff754) at adopt_std.c:934
#10 0x40143cb3 in __libc_start_main (main=0x804be8c <main>, argc=3, argv=0xbffff754, init=0x8049b6c <_init>,
fini=0x8068614 <_fini>, rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffff74c) at
../sysdeps/generic/libc-start.c:78
(gdb)
Did you download the newest ODBC driver? There have been several fixes for working with 7.1 servers. Postgresql 6.5 came with Redhat 6.2. Adam Lang Systems Engineer Rutgers Casualty Insurance Company http://www.rutgersinsurance.com ----- Original Message ----- From: "Steve Wranovsky" <stevew@merge.com> To: <pgsql-odbc@postgresql.org> Sent: Wednesday, February 07, 2001 12:21 PM Subject: 7.1 beta 4 ODBC Connection Problem > Hello, > > I have been successfully using 7.0.2 with our application under Redhat 6.0. > I was using the 7.0.2 RPMs that come with RedHat 6.2. > > I decided to test the 7.1 beta 4 with our application, and installed the > RPMs from the PostgreSQL.org ftp site. I was able to install everything, create > our database and check it with psql, however, when I try and access the database > via ODBC, I run into problems. > > I get a seg fault when I try and connect to the database via SQLConnect. Below > is a stack trace from teh core file. The crash occurs in sprintf. I'm unsure > if there are perhaps some incompatibilities between my environment and the RPMs > installed, or if this is a bug in the 7.1beta4 code. Does anyone have > any ideas? > > Thanks, > Steve > > [mergeark@steveark mergeark]$ gdb adopt_std core > GNU gdb 4.17.0.11 with Linux support > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-redhat-linux"... > Core was generated by `adopt_std /dev/scd0 1'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /home/mergeark/exe/lib/libmergebox.so...done. > Reading symbols from /usr/lib/libpsqlodbc.so.0...done. > Reading symbols from /home/mergeark/exe/lib/mc3adv.so...done. > Reading symbols from /lib/libm.so.6...done. > Reading symbols from /lib/libdl.so.2...done. > Reading symbols from /lib/libc.so.6...done. > Reading symbols from /lib/ld-linux.so.2...done. > Reading symbols from /lib/libnss_files.so.2...done. > #0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 "%c.%c", ap=0xbfffd8ac) at vfprintf.c:1248 > vfprintf.c:1248: No such file or directory. > (gdb) bt > #0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 "%c.%c", ap=0xbfffd8ac) at vfprintf.c:1248 > #1 0x4017e0b3 in _IO_vsprintf (string=0x400643df "0.0", format=0x40064409 "%c.%c", args=0xbfffd8a8) at iovsprintf.c:47 > #2 0x4017876f in sprintf (s=0x400643df "0.0", format=0x40064409 "%c.%c") at sprintf.c:38 > #3 0x4004f268 in CC_lookup_pg_version () > #4 0x4004def9 in CC_connect () > #5 0x4004d0b4 in SQLConnect () > #6 0x8057efa in DatabaseConnect () > #7 0x8057c1e in ADB_DatabaseInit () > #8 0x804a802 in Initialize_Process () at adopt_std.c:238 > #9 0x804bf7b in main (ac=3, av=0xbffff754) at adopt_std.c:934 > #10 0x40143cb3 in __libc_start_main (main=0x804be8c <main>, argc=3, argv=0xbffff754, init=0x8049b6c <_init>, > fini=0x8068614 <_fini>, rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffff74c) at ../sysdeps/generic/libc-start.c:78 > (gdb)
Adam, I uninstalled the 7.0.2 RPMS (including the ODBC driver), and installed the following RPMS: postgresql-server-7.1beta4-1 postgresql-odbc-7.1beta4-1 postgresql-7.1beta4-1 postgresql-devel-7.1beta4-1 So, this should be the latest ODBC driver, I assume. You're right, I was mistaken about my source of the 7.0.2 RPMs. I actually downloaded them from the RedHat's web site. Steve At 12:51 PM 2/7/01 -0500, Adam Lang wrote: >Did you download the newest ODBC driver? There have been several fixes for >working with 7.1 servers. > >Postgresql 6.5 came with Redhat 6.2. > >Adam Lang >Systems Engineer >Rutgers Casualty Insurance Company >http://www.rutgersinsurance.com >----- Original Message ----- >From: "Steve Wranovsky" <stevew@merge.com> >To: <pgsql-odbc@postgresql.org> >Sent: Wednesday, February 07, 2001 12:21 PM >Subject: 7.1 beta 4 ODBC Connection Problem > > >> Hello, >> >> I have been successfully using 7.0.2 with our application under Redhat >6.0. >> I was using the 7.0.2 RPMs that come with RedHat 6.2. >> >> I decided to test the 7.1 beta 4 with our application, and installed the >> RPMs from the PostgreSQL.org ftp site. I was able to install everything, >create >> our database and check it with psql, however, when I try and access the >database >> via ODBC, I run into problems. >> >> I get a seg fault when I try and connect to the database via SQLConnect. >Below >> is a stack trace from teh core file. The crash occurs in sprintf. I'm >unsure >> if there are perhaps some incompatibilities between my environment and the >RPMs >> installed, or if this is a bug in the 7.1beta4 code. Does anyone have >> any ideas? >> >> Thanks, >> Steve >> >> [mergeark@steveark mergeark]$ gdb adopt_std core >> GNU gdb 4.17.0.11 with Linux support >> Copyright 1998 Free Software Foundation, Inc. >> GDB is free software, covered by the GNU General Public License, and you >are >> welcome to change it and/or distribute copies of it under certain >conditions. >> Type "show copying" to see the conditions. >> There is absolutely no warranty for GDB. Type "show warranty" for >details. >> This GDB was configured as "i386-redhat-linux"... >> Core was generated by `adopt_std /dev/scd0 1'. >> Program terminated with signal 11, Segmentation fault. >> Reading symbols from /home/mergeark/exe/lib/libmergebox.so...done. >> Reading symbols from /usr/lib/libpsqlodbc.so.0...done. >> Reading symbols from /home/mergeark/exe/lib/mc3adv.so...done. >> Reading symbols from /lib/libm.so.6...done. >> Reading symbols from /lib/libdl.so.2...done. >> Reading symbols from /lib/libc.so.6...done. >> Reading symbols from /lib/ld-linux.so.2...done. >> Reading symbols from /lib/libnss_files.so.2...done. >> #0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 "%c.%c", >ap=0xbfffd8ac) at vfprintf.c:1248 >> vfprintf.c:1248: No such file or directory. >> (gdb) bt >> #0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 "%c.%c", >ap=0xbfffd8ac) at vfprintf.c:1248 >> #1 0x4017e0b3 in _IO_vsprintf (string=0x400643df "0.0", format=0x40064409 >"%c.%c", args=0xbfffd8a8) at iovsprintf.c:47 >> #2 0x4017876f in sprintf (s=0x400643df "0.0", format=0x40064409 "%c.%c") >at sprintf.c:38 >> #3 0x4004f268 in CC_lookup_pg_version () >> #4 0x4004def9 in CC_connect () >> #5 0x4004d0b4 in SQLConnect () >> #6 0x8057efa in DatabaseConnect () >> #7 0x8057c1e in ADB_DatabaseInit () >> #8 0x804a802 in Initialize_Process () at adopt_std.c:238 >> #9 0x804bf7b in main (ac=3, av=0xbffff754) at adopt_std.c:934 >> #10 0x40143cb3 in __libc_start_main (main=0x804be8c <main>, argc=3, >argv=0xbffff754, init=0x8049b6c <_init>, >> fini=0x8068614 <_fini>, rtld_fini=0x4000a350 <_dl_fini>, >stack_end=0xbffff74c) at ../sysdeps/generic/libc-start.c:78 >> (gdb)
Oh, you're not using ODBC on Windows? Adam Lang Systems Engineer Rutgers Casualty Insurance Company http://www.rutgersinsurance.com ----- Original Message ----- From: "Steve Wranovsky" <stevew@merge.com> To: "Adam Lang" <aalang@rutgersinsurance.com> Cc: <pgsql-odbc@postgresql.org> Sent: Wednesday, February 07, 2001 12:52 PM Subject: Re: [ODBC] Re: 7.1 beta 4 ODBC Connection Problem > Adam, > > I uninstalled the 7.0.2 RPMS (including the ODBC driver), and > installed the following RPMS: > > postgresql-server-7.1beta4-1 > postgresql-odbc-7.1beta4-1 > postgresql-7.1beta4-1 > postgresql-devel-7.1beta4-1 > > So, this should be the latest ODBC driver, I assume. > > You're right, I was mistaken about my source of the 7.0.2 RPMs. I > actually downloaded them from the RedHat's web site. > > Steve > > At 12:51 PM 2/7/01 -0500, Adam Lang wrote: > >Did you download the newest ODBC driver? There have been several fixes for > >working with 7.1 servers. > > > >Postgresql 6.5 came with Redhat 6.2. > > > >Adam Lang > >Systems Engineer > >Rutgers Casualty Insurance Company > >http://www.rutgersinsurance.com > >----- Original Message ----- > >From: "Steve Wranovsky" <stevew@merge.com> > >To: <pgsql-odbc@postgresql.org> > >Sent: Wednesday, February 07, 2001 12:21 PM > >Subject: 7.1 beta 4 ODBC Connection Problem > > > > > >> Hello, > >> > >> I have been successfully using 7.0.2 with our application under Redhat > >6.0. > >> I was using the 7.0.2 RPMs that come with RedHat 6.2. > >> > >> I decided to test the 7.1 beta 4 with our application, and installed the > >> RPMs from the PostgreSQL.org ftp site. I was able to install everything, > >create > >> our database and check it with psql, however, when I try and access the > >database > >> via ODBC, I run into problems. > >> > >> I get a seg fault when I try and connect to the database via SQLConnect. > >Below > >> is a stack trace from teh core file. The crash occurs in sprintf. I'm > >unsure > >> if there are perhaps some incompatibilities between my environment and the > >RPMs > >> installed, or if this is a bug in the 7.1beta4 code. Does anyone have > >> any ideas? > >> > >> Thanks, > >> Steve > >> > >> [mergeark@steveark mergeark]$ gdb adopt_std core > >> GNU gdb 4.17.0.11 with Linux support > >> Copyright 1998 Free Software Foundation, Inc. > >> GDB is free software, covered by the GNU General Public License, and you > >are > >> welcome to change it and/or distribute copies of it under certain > >conditions. > >> Type "show copying" to see the conditions. > >> There is absolutely no warranty for GDB. Type "show warranty" for > >details. > >> This GDB was configured as "i386-redhat-linux"... > >> Core was generated by `adopt_std /dev/scd0 1'. > >> Program terminated with signal 11, Segmentation fault. > >> Reading symbols from /home/mergeark/exe/lib/libmergebox.so...done. > >> Reading symbols from /usr/lib/libpsqlodbc.so.0...done. > >> Reading symbols from /home/mergeark/exe/lib/mc3adv.so...done. > >> Reading symbols from /lib/libm.so.6...done. > >> Reading symbols from /lib/libdl.so.2...done. > >> Reading symbols from /lib/libc.so.6...done. > >> Reading symbols from /lib/ld-linux.so.2...done. > >> Reading symbols from /lib/libnss_files.so.2...done. > >> #0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 "%c.%c", > >ap=0xbfffd8ac) at vfprintf.c:1248 > >> vfprintf.c:1248: No such file or directory. > >> (gdb) bt > >> #0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 "%c.%c", > >ap=0xbfffd8ac) at vfprintf.c:1248 > >> #1 0x4017e0b3 in _IO_vsprintf (string=0x400643df "0.0", format=0x40064409 > >"%c.%c", args=0xbfffd8a8) at iovsprintf.c:47 > >> #2 0x4017876f in sprintf (s=0x400643df "0.0", format=0x40064409 "%c.%c") > >at sprintf.c:38 > >> #3 0x4004f268 in CC_lookup_pg_version () > >> #4 0x4004def9 in CC_connect () > >> #5 0x4004d0b4 in SQLConnect () > >> #6 0x8057efa in DatabaseConnect () > >> #7 0x8057c1e in ADB_DatabaseInit () > >> #8 0x804a802 in Initialize_Process () at adopt_std.c:238 > >> #9 0x804bf7b in main (ac=3, av=0xbffff754) at adopt_std.c:934 > >> #10 0x40143cb3 in __libc_start_main (main=0x804be8c <main>, argc=3, > >argv=0xbffff754, init=0x8049b6c <_init>, > >> fini=0x8068614 <_fini>, rtld_fini=0x4000a350 <_dl_fini>, > >stack_end=0xbffff74c) at ../sysdeps/generic/libc-start.c:78 > >> (gdb)
Adam, No, I'm actually using the ODBC interface under Linux. Should I be sending this to another mailing list? Steve At 01:05 PM 2/7/01 -0500, Adam Lang wrote: >Oh, you're not using ODBC on Windows? > >Adam Lang >Systems Engineer >Rutgers Casualty Insurance Company >http://www.rutgersinsurance.com >----- Original Message ----- >From: "Steve Wranovsky" <stevew@merge.com> >To: "Adam Lang" <aalang@rutgersinsurance.com> >Cc: <pgsql-odbc@postgresql.org> >Sent: Wednesday, February 07, 2001 12:52 PM >Subject: Re: [ODBC] Re: 7.1 beta 4 ODBC Connection Problem > > >> Adam, >> >> I uninstalled the 7.0.2 RPMS (including the ODBC driver), and >> installed the following RPMS: >> >> postgresql-server-7.1beta4-1 >> postgresql-odbc-7.1beta4-1 >> postgresql-7.1beta4-1 >> postgresql-devel-7.1beta4-1 >> >> So, this should be the latest ODBC driver, I assume. >> >> You're right, I was mistaken about my source of the 7.0.2 RPMs. I >> actually downloaded them from the RedHat's web site. >> >> Steve >> >> At 12:51 PM 2/7/01 -0500, Adam Lang wrote: >> >Did you download the newest ODBC driver? There have been several fixes >for >> >working with 7.1 servers. >> > >> >Postgresql 6.5 came with Redhat 6.2. >> > >> >Adam Lang >> >Systems Engineer >> >Rutgers Casualty Insurance Company >> >http://www.rutgersinsurance.com >> >----- Original Message ----- >> >From: "Steve Wranovsky" <stevew@merge.com> >> >To: <pgsql-odbc@postgresql.org> >> >Sent: Wednesday, February 07, 2001 12:21 PM >> >Subject: 7.1 beta 4 ODBC Connection Problem >> > >> > >> >> Hello, >> >> >> >> I have been successfully using 7.0.2 with our application under Redhat >> >6.0. >> >> I was using the 7.0.2 RPMs that come with RedHat 6.2. >> >> >> >> I decided to test the 7.1 beta 4 with our application, and installed >the >> >> RPMs from the PostgreSQL.org ftp site. I was able to install >everything, >> >create >> >> our database and check it with psql, however, when I try and access the >> >database >> >> via ODBC, I run into problems. >> >> >> >> I get a seg fault when I try and connect to the database via >SQLConnect. >> >Below >> >> is a stack trace from teh core file. The crash occurs in sprintf. I'm >> >unsure >> >> if there are perhaps some incompatibilities between my environment and >the >> >RPMs >> >> installed, or if this is a bug in the 7.1beta4 code. Does anyone have >> >> any ideas? >> >> >> >> Thanks, >> >> Steve >> >> >> >> [mergeark@steveark mergeark]$ gdb adopt_std core >> >> GNU gdb 4.17.0.11 with Linux support >> >> Copyright 1998 Free Software Foundation, Inc. >> >> GDB is free software, covered by the GNU General Public License, and >you >> >are >> >> welcome to change it and/or distribute copies of it under certain >> >conditions. >> >> Type "show copying" to see the conditions. >> >> There is absolutely no warranty for GDB. Type "show warranty" for >> >details. >> >> This GDB was configured as "i386-redhat-linux"... >> >> Core was generated by `adopt_std /dev/scd0 1'. >> >> Program terminated with signal 11, Segmentation fault. >> >> Reading symbols from /home/mergeark/exe/lib/libmergebox.so...done. >> >> Reading symbols from /usr/lib/libpsqlodbc.so.0...done. >> >> Reading symbols from /home/mergeark/exe/lib/mc3adv.so...done. >> >> Reading symbols from /lib/libm.so.6...done. >> >> Reading symbols from /lib/libdl.so.2...done. >> >> Reading symbols from /lib/libc.so.6...done. >> >> Reading symbols from /lib/ld-linux.so.2...done. >> >> Reading symbols from /lib/libnss_files.so.2...done. >> >> #0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 >"%c.%c", >> >ap=0xbfffd8ac) at vfprintf.c:1248 >> >> vfprintf.c:1248: No such file or directory. >> >> (gdb) bt >> >> #0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 >"%c.%c", >> >ap=0xbfffd8ac) at vfprintf.c:1248 >> >> #1 0x4017e0b3 in _IO_vsprintf (string=0x400643df "0.0", >format=0x40064409 >> >"%c.%c", args=0xbfffd8a8) at iovsprintf.c:47 >> >> #2 0x4017876f in sprintf (s=0x400643df "0.0", format=0x40064409 >"%c.%c") >> >at sprintf.c:38 >> >> #3 0x4004f268 in CC_lookup_pg_version () >> >> #4 0x4004def9 in CC_connect () >> >> #5 0x4004d0b4 in SQLConnect () >> >> #6 0x8057efa in DatabaseConnect () >> >> #7 0x8057c1e in ADB_DatabaseInit () >> >> #8 0x804a802 in Initialize_Process () at adopt_std.c:238 >> >> #9 0x804bf7b in main (ac=3, av=0xbffff754) at adopt_std.c:934 >> >> #10 0x40143cb3 in __libc_start_main (main=0x804be8c <main>, argc=3, >> >argv=0xbffff754, init=0x8049b6c <_init>, >> >> fini=0x8068614 <_fini>, rtld_fini=0x4000a350 <_dl_fini>, >> >stack_end=0xbffff74c) at ../sysdeps/generic/libc-start.c:78 >> >> (gdb)
No, here is fine... I was just assuming you were using ODBC for a Windows app to interact with postgres on Linux. Sorry, I know nothing of ODBC on Linux. :) Adam Lang Systems Engineer Rutgers Casualty Insurance Company http://www.rutgersinsurance.com ----- Original Message ----- From: "Steve Wranovsky" <stevew@merge.com> To: "Adam Lang" <aalang@rutgersinsurance.com> Cc: <pgsql-odbc@postgresql.org> Sent: Wednesday, February 07, 2001 1:03 PM Subject: Re: Re: 7.1 beta 4 ODBC Connection Problem > Adam, > > No, I'm actually using the ODBC interface under Linux. Should > I be sending this to another mailing list? > > Steve > > > > At 01:05 PM 2/7/01 -0500, Adam Lang wrote: > >Oh, you're not using ODBC on Windows? > > > >Adam Lang > >Systems Engineer > >Rutgers Casualty Insurance Company > >http://www.rutgersinsurance.com > >----- Original Message ----- > >From: "Steve Wranovsky" <stevew@merge.com> > >To: "Adam Lang" <aalang@rutgersinsurance.com> > >Cc: <pgsql-odbc@postgresql.org> > >Sent: Wednesday, February 07, 2001 12:52 PM > >Subject: Re: [ODBC] Re: 7.1 beta 4 ODBC Connection Problem > > > > > >> Adam, > >> > >> I uninstalled the 7.0.2 RPMS (including the ODBC driver), and > >> installed the following RPMS: > >> > >> postgresql-server-7.1beta4-1 > >> postgresql-odbc-7.1beta4-1 > >> postgresql-7.1beta4-1 > >> postgresql-devel-7.1beta4-1 > >> > >> So, this should be the latest ODBC driver, I assume. > >> > >> You're right, I was mistaken about my source of the 7.0.2 RPMs. I > >> actually downloaded them from the RedHat's web site. > >> > >> Steve > >> > >> At 12:51 PM 2/7/01 -0500, Adam Lang wrote: > >> >Did you download the newest ODBC driver? There have been several fixes > >for > >> >working with 7.1 servers. > >> > > >> >Postgresql 6.5 came with Redhat 6.2. > >> > > >> >Adam Lang > >> >Systems Engineer > >> >Rutgers Casualty Insurance Company > >> >http://www.rutgersinsurance.com > >> >----- Original Message ----- > >> >From: "Steve Wranovsky" <stevew@merge.com> > >> >To: <pgsql-odbc@postgresql.org> > >> >Sent: Wednesday, February 07, 2001 12:21 PM > >> >Subject: 7.1 beta 4 ODBC Connection Problem > >> > > >> > > >> >> Hello, > >> >> > >> >> I have been successfully using 7.0.2 with our application under Redhat > >> >6.0. > >> >> I was using the 7.0.2 RPMs that come with RedHat 6.2. > >> >> > >> >> I decided to test the 7.1 beta 4 with our application, and installed > >the > >> >> RPMs from the PostgreSQL.org ftp site. I was able to install > >everything, > >> >create > >> >> our database and check it with psql, however, when I try and access the > >> >database > >> >> via ODBC, I run into problems. > >> >> > >> >> I get a seg fault when I try and connect to the database via > >SQLConnect. > >> >Below > >> >> is a stack trace from teh core file. The crash occurs in sprintf. I'm > >> >unsure > >> >> if there are perhaps some incompatibilities between my environment and > >the > >> >RPMs > >> >> installed, or if this is a bug in the 7.1beta4 code. Does anyone have > >> >> any ideas? > >> >> > >> >> Thanks, > >> >> Steve > >> >> > >> >> [mergeark@steveark mergeark]$ gdb adopt_std core > >> >> GNU gdb 4.17.0.11 with Linux support > >> >> Copyright 1998 Free Software Foundation, Inc. > >> >> GDB is free software, covered by the GNU General Public License, and > >you > >> >are > >> >> welcome to change it and/or distribute copies of it under certain > >> >conditions. > >> >> Type "show copying" to see the conditions. > >> >> There is absolutely no warranty for GDB. Type "show warranty" for > >> >details. > >> >> This GDB was configured as "i386-redhat-linux"... > >> >> Core was generated by `adopt_std /dev/scd0 1'. > >> >> Program terminated with signal 11, Segmentation fault. > >> >> Reading symbols from /home/mergeark/exe/lib/libmergebox.so...done. > >> >> Reading symbols from /usr/lib/libpsqlodbc.so.0...done. > >> >> Reading symbols from /home/mergeark/exe/lib/mc3adv.so...done. > >> >> Reading symbols from /lib/libm.so.6...done. > >> >> Reading symbols from /lib/libdl.so.2...done. > >> >> Reading symbols from /lib/libc.so.6...done. > >> >> Reading symbols from /lib/ld-linux.so.2...done. > >> >> Reading symbols from /lib/libnss_files.so.2...done. > >> >> #0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 > >"%c.%c", > >> >ap=0xbfffd8ac) at vfprintf.c:1248 > >> >> vfprintf.c:1248: No such file or directory. > >> >> (gdb) bt > >> >> #0 0x40171e23 in _IO_vfprintf (s=0xbfffd7e0, format=0x40064409 > >"%c.%c", > >> >ap=0xbfffd8ac) at vfprintf.c:1248 > >> >> #1 0x4017e0b3 in _IO_vsprintf (string=0x400643df "0.0", > >format=0x40064409 > >> >"%c.%c", args=0xbfffd8a8) at iovsprintf.c:47 > >> >> #2 0x4017876f in sprintf (s=0x400643df "0.0", format=0x40064409 > >"%c.%c") > >> >at sprintf.c:38 > >> >> #3 0x4004f268 in CC_lookup_pg_version () > >> >> #4 0x4004def9 in CC_connect () > >> >> #5 0x4004d0b4 in SQLConnect () > >> >> #6 0x8057efa in DatabaseConnect () > >> >> #7 0x8057c1e in ADB_DatabaseInit () > >> >> #8 0x804a802 in Initialize_Process () at adopt_std.c:238 > >> >> #9 0x804bf7b in main (ac=3, av=0xbffff754) at adopt_std.c:934 > >> >> #10 0x40143cb3 in __libc_start_main (main=0x804be8c <main>, argc=3, > >> >argv=0xbffff754, init=0x8049b6c <_init>, > >> >> fini=0x8068614 <_fini>, rtld_fini=0x4000a350 <_dl_fini>, > >> >stack_end=0xbffff74c) at ../sysdeps/generic/libc-start.c:78 > >> >> (gdb)
> -----Original Message----- > From: Steve Wranovsky [mailto:stevew@merge.com] > Sent: 07 February 2001 17:21 > To: pgsql-odbc@postgresql.org > Subject: [ODBC] 7.1 beta 4 ODBC Connection Problem > > > Hello, > > I have been successfully using 7.0.2 with our application > under Redhat 6.0. > I was using the 7.0.2 RPMs that come with RedHat 6.2. > <snip> The code that you appear to have crashed at has been tweeked very recently (I believe since beta4). Can you try the code currently in CVS? Regards, Dave.