| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Nick Raj <nickrajjain(at)gmail(dot)com>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Debug contrib/cube code |
| Date: | 2011-05-13 17:13:23 |
| Message-ID: | 937.1305306803@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, May 13, 2011 at 12:12 PM, Nick Raj <nickrajjain(at)gmail(dot)com> wrote:
>> Can you throw some light on how to debug contrib/cube code?
> On my system, if I configure --enable-debug, the contrib modules are
> compiled with debug support as well.
Depending on what platform you're using, it may be hard to get
breakpoints in dynamically loaded modules to work. On many platforms it
helps to make sure that the module is loaded before you attach to the
backend process with gdb. To do that, you can either call one of its
functions, or just do a manual LOAD command.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2011-05-13 19:48:36 | hint bit cache v6 |
| Previous Message | Robert Haas | 2011-05-13 16:51:15 | Re: Debug contrib/cube code |