| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | HuangQi <huangqiyx(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: gdb with postgres |
| Date: | 2011-06-06 13:55:15 |
| Message-ID: | BANLkTinuZf_dyUue+G2XwJ9yZY1cerxasw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 6, 2011 at 9:47 AM, HuangQi <huangqiyx(at)gmail(dot)com> wrote:
> If I enter c, gdb will directly finish executing this process and current
> query will finish. Furthermore, if I enter next query, gdb will not debug it
> and stay in continue status.
Hmm, that must mean your breakpoint isn't properly set.
Instead of doing gdb postgres and then using attach, try just doing
gdb -p PIDNAME, then set your breakpoint, then continue. That's how
I've always done it, anyway...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-06-06 13:57:36 | Re: gdb with postgres |
| Previous Message | HuangQi | 2011-06-06 13:47:06 | Re: gdb with postgres |