Thanks very much for the suggestions! will try them out
regards,
Shreya
Sibte Abbas <[EMAIL PROTECTED]> wrote:
On 7/22/07, Sibte Abbas wrote:
> On 7/22/07, Tom Lane wrote:
> > Shreya Bhargava writes:
> > > 1. gdb postgres
> > > 2. set args -D test (test is my dbcluster)
> > > 3. b h
On 7/22/07, Sibte Abbas <[EMAIL PROTECTED]> wrote:
On 7/22/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> Shreya Bhargava <[EMAIL PROTECTED]> writes:
> > 1. gdb postgres
> > 2. set args -D test (test is my dbcluster)
> > 3. b hashbuild(this is the function i want to break on)
> > 4. run
>
> You've set
On 7/22/07, Tom Lane <[EMAIL PROTECTED]> wrote:
Shreya Bhargava <[EMAIL PROTECTED]> writes:
> 1. gdb postgres
> 2. set args -D test (test is my dbcluster)
> 3. b hashbuild(this is the function i want to break on)
> 4. run
You've set the breakpoint in the postmaster process. It won't propagate
t
Shreya Bhargava <[EMAIL PROTECTED]> writes:
> 1. gdb postgres
> 2. set args -D test (test is my dbcluster)
> 3. b hashbuild(this is the function i want to break on)
> 4. run
You've set the breakpoint in the postmaster process. It won't propagate
to child backends, at least not without special gdb
Hi,
I am trying to debug postgres source code using gdb. I set a breakpoint on a
function, but it never stops when it reaches that function. Here are the steps:
1. gdb postgres
2. set args -D test (test is my dbcluster)
3. b hashbuild(this is the function i want to break on)
4. run
5. start a cl
