From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | [pgAdmin III] #73: Running a Properties Report on the local server results in core dump |
Date: | 2009-09-04 16:12:33 |
Message-ID: | 046.62443f35aa4beff61c090a27e8cae950@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#73: Running a Properties Report on the local server results in core dump
----------------------+-----------------------------------------------------
Reporter: dpage | Owner: dpage
Type: bug | Status: new
Priority: critical | Milestone: 1.10.1
Component: pgadmin | Version: 1.10
Keywords: | Platform: solaris
----------------------+-----------------------------------------------------
Solaris 10 11/06 s10x_u3wos_10 x86 / SPARC 10 11/06 s10s_u3wos_10 sparc
Description:
--------------
Running a Properties Report in pgAdmin on the local server results in a
core dump
Platform: Solaris x86_64
Steps to Reproduce:
----------------------
1. Install PPAS8.3R2AS on Solaris x86_64.
2. Launch pgAdmin and connect to a server running on the same local
machine
3. Right click the server and select Reports -> Properties Report.
4. Enter path/filename for output file and click OK
This error is seen in the terminal after the pgAdmin GUI exits.
(pgadmin3.bin: 6777) GLib-GObject-CRITICAL **: file gobject.c: line 1222:
assertion 'G_IS_OBJECT (object)' failed
Segmentation fault(core dumped)
Expected:
-----------
Report should be generated and the application should not result in a seg
fault/core dump.
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/73>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | pgAdmin Trac | 2009-09-04 16:13:07 | Re: [pgAdmin III] #73: Running a Properties Report on the local server results in core dump |
Previous Message | pgAdmin Trac | 2009-09-04 16:10:55 | [pgAdmin III] #72: Database name contains Chinese chars then debugging procedure/function in it results in core dump |