Thread: [pgAdmin III] #72: Database name contains Chinese chars then debugging procedure/function in it results in core dump

#72: Database name contains Chinese chars then debugging procedure/function in
it 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
----------------------+-----------------------------------------------------
 Platform:  Solaris 10 Sparc
 -----------
 pgAdmin Version  1.10.0(Jul 21 2009, rev 7976)

 Description:
 --------------
 If the database name contains Chinese characters and debugger is launched
 on a procedure/function created in that database then pgAdmin exits and
 Segmentation Fault(core dumped) error is seen on the console.


 Steps to Reproduce:
 ----------------------
 1. Launch pgadmin and connect to server.
 2. Create a new database and enter Chinese characters for the database
 name.
 3. Create a function/procedure/package.
 4. Right click the procedure/function and select Debugging-> Debug

 pgAdmin exits and error is seen on the console.


 Expected:
 ------------
 Debugger should launch properly and pgAdmin should not exit.

--
Ticket URL: <http://code.pgadmin.org/trac/ticket/72>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

#72: Database name contains Chinese chars then debugging procedure/function in
it results in core dump
----------------------+-----------------------------------------------------
 Reporter:  dpage     |       Owner:  dpage  
     Type:  bug       |      Status:  new    
 Priority:  critical  |   Milestone:         
Component:  pgadmin   |     Version:  1.10   
 Keywords:            |    Platform:  solaris
----------------------+-----------------------------------------------------
Changes (by gleu):

  * milestone:  1.10.2 =>


--
Ticket URL: <http://code.pgadmin.org/trac/ticket/72#comment:1>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III