Belay that, you should be able to put a breakpoint on errstart or elog
or perhaps errmsg. Much easier...
(I expected the find the answer in the developer FAQ, but it's not
there).
Hope this helps,
On Thu, Oct 27, 2005 at 12:04:45PM +0200, Martijn van Oosterhout wrote:
> On Thu, Oct 27, 2005 at 11:37:09AM +0200, Matteo Beccati wrote:
> > Here is the backtrace, hoping I did it correctly:
>
> Dagnammit. I was wondering if that was going to happen. If your
> optimisation is up, the values of arguments to the functions don't
> display right (look at the rest, they're obviously not correct). While
> it's possible there's a bug that early in the output, I wouldn't bet on
> it.
>
> The trick (other than turning off optimisation) is to set the
> breakpoint a few lines later, like say mcxt.c:504. You can find out by
> simply stepping the debugger until "p size" displays a reasonable
> value.
>
> try with: break mcxt.c:504 if size > 1000000000
>
> Hope this helps,
> --
> Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> > tool for doing 5% of the work and then sitting around waiting for someone
> > else to do the other 95% so you can sue them.
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
