To connect a debbuger... - Mailing list pgsql-hackers

From Jonathan Scher
Subject To connect a debbuger...
Date
Msg-id 45F59CDC.5060002@oxado.com
Whole thread Raw
Responses Re: To connect a debbuger...
List pgsql-hackers
Hello!

I'm trying to add some features to PostgreSQL, but I just can't figure 
out how to make gdb work with it.

I attach gdb to /usr/.../bin/postgres, then I put a breakpoint. Whenever 
postgres stop on that breakpoint, it just kills/restarts the server 
instead of asking me what to do.

It's surely a noob's question but how can I use a debugger with PostegreSQL?

Regards,
Jonathan Scher

(gdb) file  /usr/local/pgsql/bin/postgres
Reading symbols from /usr/local/pgsql/bin/postgres...(no debugging 
symbols found)...done.
(gdb) set args -D /home/heziva/pgsql/pgsql_data/
(gdb) b transformFromClause
Breakpoint 1 at 0x80e371e
(gdb) r
Starting program: /usr/local/pgsql/bin/postgres -D 
/home/heziva/pgsql/pgsql_data/
(no debugging symbols found)...(no debugging symbols found)...(no 
debugging symbols found)...(no debugging symbols found)...LOG:  database 
system was interrupted; last known up at 2007-03-12 18:04:04 UTC
LOG:  checkpoint record is at 0/481504
LOG:  redo record is at 0/481504; shutdown TRUE
LOG:  next transaction ID: 0/710; next OID: 16392
LOG:  next MultiXactId: 1; next MultiXactOffset: 0
LOG:  database system was not properly shut down; automatic recovery in 
progress
LOG:  record with zero length at 0/481544
LOG:  redo is not required
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started

=====> on another shell.... psql....\d

(gdb) file  /usr/local/pgsql/bin/postgres
Reading symbols from /usr/local/pgsql/bin/postgres...(no debugging 
symbols found)...done.
(gdb) set args -D /home/heziva/pgsql/pgsql_data/
(gdb) b transformFromClause
Breakpoint 1 at 0x80e371e
(gdb) r
Starting program: /usr/local/pgsql/bin/postgres -D 
/home/heziva/pgsql/pgsql_data/
(no debugging symbols found)...(no debugging symbols found)...(no 
debugging symbols found)...(no debugging symbols found)...LOG:  database 
system was interrupted; last known up at 2007-03-12 18:04:04 UTC
LOG:  checkpoint record is at 0/481504
LOG:  redo record is at 0/481504; shutdown TRUE
LOG:  next transaction ID: 0/710; next OID: 16392
LOG:  next MultiXactId: 1; next MultiXactOffset: 0
LOG:  database system was not properly shut down; automatic recovery in 
progress
LOG:  record with zero length at 0/481544
LOG:  redo is not required
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started






pgsql-hackers by date:

Previous
From: "CAJ CAJ"
Date:
Subject: Re: Updating large postgresql database with blobs
Next
From: Andrew Dunstan
Date:
Subject: Re: Updating large postgresql database with blobs