Thread: Refreshing removed object crashes pgadmin3
Subject: Refreshing removed object crashes pgadmin3
Package: pgadmin3
Version: 1.0.2-0.1
Severity: important
Trying to refresh the view of an object that no longer exists in the
database (a dropped table for example), crashes pgadmin3 with a
Segmentation fault.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux deribero 2.4.22 #1 Tue Oct 7 17:44:55 CEST 2003 i686
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages pgadmin3 depends on:
ii libatk1.0-0 1.4.1-1 The ATK accessibility toolkit
ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an
ii libfreetype6 2.1.5-2 FreeType 2 font engine, shared lib
ii libglib2.0-0 2.2.3-1 The GLib library of C routines
ii libgtk2.0-0 2.2.1-6 The GTK+ graphical user interface
ii libjpeg62 6b-8 The Independent JPEG Group's JPEG
ii libpango1.0-0 1.2.5-1 Layout and rendering of internatio
ii libpgsql2 7.2.1-2woody4 Shared library libpq.so.2 for Post
ii libpng2 1.0.15-4 PNG library, older version - runti
ii libssl0.9.6 0.9.6l-1 SSL shared libraries (old version)
ii libstdc++2.10-glibc2.2 1:2.95.4-17 The GNU stdc++ library
ii libtiff3g 3.5.7-2 Tag Image File Format library
ii xlibs 4.2.1-11 X Window System client libraries
ii zlib1g 1:1.2.1-3 compression library - runtime
-- no debconf information
--
Richard van den Berg, CISSP
Trust Factory B.V. | http://www.trust-factory.com/
Bazarstraat 44a | Phone: +31 70 3620684
NL-2518AK The Hague | Fax : +31 70 3603009
The Netherlands |
Visit us at Lotusphere 2004 http://www.trust-factory.com/lotusphere
Dear Richard. ----- Original Message ----- From: "Richard van den Berg" <richard.vandenberg@trust-factory.com> > Subject: Refreshing removed object crashes pgadmin3 > Package: pgadmin3 > Version: 1.0.2-0.1 > Severity: important (snip) > ii libpgsql2 7.2.1-2woody4 Shared library libpq.so.2 for Post ''''''''''''''''''''''''''''''''''''''' Hmm.. Is PostgreSQL7.2.1 in your environment? It may be a problem he had libpq made as shared. pgAdmin3 requires libpq beyond PostgreSQL7.3. regards, Hiroshi Saito
Dear Richard, Hiroshi, it seems that richard is using woody ( the debian stable release ). As I'm linking dynamically debian packages to postgre,I used the debian official postgresql package to build pgA3. I saw the thread between Jean Michel Pouré and Andreas Pflug last month concerning libpq issue (concluding to the necessityof a static linking of libpq) but did not get time to modify my packages. to pgadmin-hackers: Is it *really* a pre-req to use libpq >=7.3 ? If yes, this a pure packaging issue we have here... I think I'll have to produce different packages for woody and for testing/unstable. I would like to continue dynamic linking for testing and unstable as it's debian way to do the things. Can others (on other distros) try to reproduce the bug signaled here ? To Richard: I wait a bit for answers from others but will try a particular build for woody with static linking against apostgresql backport... that's quite a lot of work, so you'll have to wait a little. Regards, Raphaël ----Message d'origine---- >De: "Hiroshi Saito" <saito@inetrt.skcapi.co.jp> >A: "Richard van den Berg" <richard.vandenberg@trust-factory.com>, >Sujet: Re: [pgadmin-support] Refreshing removed object crashes pgadmin3 >Date: Thu, 8 Jan 2004 19:09:55 +0900 > >Dear Richard. > >----- Original Message ----- >From: "Richard van den Berg" <richard.vandenberg@trust-factory.com> > > >> Subject: Refreshing removed object crashes pgadmin3 >> Package: pgadmin3 >> Version: 1.0.2-0.1 >> Severity: important >(snip) >> ii libpgsql2 7.2.1-2woody4 Shared library libpq.so.2 for Post > ''''''''''''''''''''''''''''''''''''''' >Hmm.. >Is PostgreSQL7.2.1 in your environment? >It may be a problem he had libpq made as shared. >pgAdmin3 requires libpq beyond PostgreSQL7.3. > >regards, >Hiroshi Saito > >---------------------------(end of broadcast)--------------------------- >TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) > >
blacknoz@club-internet.fr wrote: >Dear Richard, Hiroshi, > >it seems that richard is using woody ( the debian stable release ). As I'm linking dynamically debian packages to postgre,I used the debian official postgresql package to build pgA3. > >I saw the thread between Jean Michel Pouré and Andreas Pflug last month concerning libpq issue (concluding to the necessityof a static linking of libpq) but did not get time to modify my packages. > >to pgadmin-hackers: >Is it *really* a pre-req to use libpq >=7.3 ? > > Well, we had quite some problems discovered in libs, so I'd prefer to have static 7.4.1 libpq linked to pgAdmin3 for binary distributions. Older libpqs might work, still it's kind of strange to use a 7.2.1 libpq for a tool that doesn't understand less than 7.3. >If yes, this a pure packaging issue we have here... I think I'll have to produce different packages for woody and for testing/unstable. >I would like to continue dynamic linking for testing and unstable as it's debian way to do the things. > >Can others (on other distros) try to reproduce the bug signaled here ? > > This crashes under gtk, but not under win32 for CVS head. I'll have a look at it later. Regards, Andreas
blacknoz@club-internet.fr wrote: > it seems that richard is using woody ( the debian stable release ). Actually, I am not. I'm running a mix of testing and unstable on my system. I used the stable pgadmin3 distribution however. > As I'm linking dynamically debian packages to postgre, I used the > debian official postgresql package to build pgA3. It seems there are at least 2 different debian packages of pgadmin3, both with the same name and version number, but different dependencies: ftp://ftp.eu.postgresql.org/pub/unix/db/postgresql/pgadmin3/release/debian/dists/stable/pgadmin/binary-i386/pgadmin3_1.0.2-0.1_i386.deb ftp://ftp.eu.postgresql.org/pub/unix/db/postgresql/pgadmin3/release/debian/dists/unstable/pgadmin/binary-i386/pgadmin3_1.0.2-0.1_i386.deb I installed the version from the unstable directory and now reportbug says: Versions of packages pgadmin3 depends on: ii libatk1.0-0 1.4.1-1 The ATK accessibility toolkit ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an ii libfreetype6 2.1.5-2 FreeType 2 font engine, shared lib ii libgcc1 1:3.3.3-0pre0 GCC support library ii libglib2.0-0 2.2.3-1 The GLib library of C routines ii libgtk2.0-0 2.2.1-6 The GTK+ graphical user interface ii libjpeg62 6b-8 The Independent JPEG Group's JPEG ii libpango1.0-0 1.2.5-1 Layout and rendering of internatio ii libpng12-0 1.2.5.0-4 PNG library - runtime ii libpq3 7.4.1-1 Shared library libpq.so.3 for Post ii libssl0.9.7 0.9.7c-1 SSL shared libraries ii libstdc++5 1:3.3.3-0pre0 The GNU Standard C++ Library v3 ii libtiff3g 3.5.7-2 Tag Image File Format library ii xlibs 4.2.1-11 X Window System client libraries ii zlib1g 1:1.2.1-3 compression library - runtime The bug I originally reported (segfault when refreshing a removed object) is still there. -- Richard van den Berg, CISSP Trust Factory B.V. | http://www.trust-factory.com/ Bazarstraat 44a | Phone: +31 70 3620684 NL-2518AK The Hague | Fax : +31 70 3603009 The Netherlands | Visit us at Lotusphere 2004 http://www.trust-factory.com/lotusphere
----Message d'origine---- >Date: Thu, 08 Jan 2004 16:13:54 +0100 >De: Richard van den Berg <richard.vandenberg@trust-factory.com> >A: blacknoz@club-internet.fr >Copie à: saito@inetrt.skcapi.co.jp, pgadmin-support@postgresql.org, >Sujet: Re: [pgadmin-support] Refreshing removed object crashes pgadmin3 > >blacknoz@club-internet.fr wrote: > >It seems there are at least 2 different debian packages of pgadmin3, >both with the same name and version number, but different dependencies: In fact there should be three package with the same name and different dependencies. stable, testing, unstable correspondto the debian release you are using. As you are on a testing/unstable, you should definitely not use the stable repository but at least the testing or unstable. They are all build of the same source in different repositories. (it's longer explained at http://www.pgadmin.org/pgadmin3/download.ph Please, feel free to tell me if it's not clear enough). As you are using a mix between testing and unstable, your /etc/apt/sources.list should contain: deb ftp://ftp.eu.postgresql.org/pub/unix/db/postgresql/pgadmin3/release/debian testing pgadmin OR : deb ftp://ftp.eu.postgresql.org/pub/unix/db/postgresql/pgadmin3/release/debian unstable pgadmin (on a single line) >The bug I originally reported (segfault when refreshing a removed >object) is still there. Ok, that's what Andreas told, it seems to crash with a gtk environment but not on a win32 one... Andreas, will surely find a solution. It's not a debian specific issue. Thank you for your report, and feel free to contact me if I was not clear enough. Regards, Raphaël
Richard van den Berg wrote: > Subject: Refreshing removed object crashes pgadmin3 > Package: pgadmin3 > Version: 1.0.2-0.1 > Severity: important > > > > Trying to refresh the view of an object that no longer exists in the > database (a dropped table for example), crashes pgadmin3 with a > Segmentation fault. > Fixed in CVS. Regards, Andreas