On Wed, 15 Feb 2006, Tom Lane wrote:
> Andrew Klosterman <[EMAIL PROTECTED]> writes:
> > With the debug binaries, I was able to step through the program and get to
> > what appears to be the function where it bails: line 1166 of
> > postgresql-8.1.0/src/interfaces/libpq/fe-secure.c where SSL_free
Andrew Klosterman <[EMAIL PROTECTED]> writes:
> With the debug binaries, I was able to step through the program and get to
> what appears to be the function where it bails: line 1166 of
> postgresql-8.1.0/src/interfaces/libpq/fe-secure.c where SSL_free() is
> called.
BTW, is the address that glib
On Mon, 13 Feb 2006, Stephen Frost wrote:
> Hmm, alright, well, this is at least not the fault of the patch of mine
> which was included in Debian's 8.1.2-2 Postgres release. :) You might
> try compiling some debs with debugging enabled. This is (reasonably)
> straight-forward:
>
> (as root:)
>
> > Tracking down exactly what's tickling the problem in this case could be
> > tricky...
>
> Yeah :-(. If you aren't able to narrow it further by yourself, please
> try to put together a self-contained test case.
>
> regards, tom lane
Well, my attempt last night at putting
> We may be spending too much time on this one point --- as long as
> Kerberos isn't *writing* into the zero-length alloc, there is nothing
> illegal immoral or fattening about malloc(0). Can you get ElectricFence
> to not abort right here but continue on to the real problem?
>
>
On Tue, 14 Feb 2006, Stephen Frost wrote:
> It's kind of a chicken-and-egg here because the backend decides what
> authentication mechanism to ask for based off the username (at least in
> part) through pg_hba.conf, so you can't find out the authentication
> method until you know the username so a
On Tue, 14 Feb 2006, Andrew Klosterman wrote:
> On Mon, 13 Feb 2006, Stephen Frost wrote:
>
> > Hmm, alright, well, this is at least not the fault of the patch of mine
> > which was included in Debian's 8.1.2-2 Postgres release. :) You might
> > try compiling some debs with debugging enabled. Th
On Tue, 14 Feb 2006, Andrew Klosterman wrote:
> > We may be spending too much time on this one point --- as long as
> > Kerberos isn't *writing* into the zero-length alloc, there is nothing
> > illegal immoral or fattening about malloc(0). Can you get ElectricFence
> > to not abort right here but
On Tue, 14 Feb 2006, Jens-Wolfhard Schicke wrote:
> --On Montag, Februar 13, 2006 21:25:30 -0500 Stephen Frost
> <[EMAIL PROTECTED]> wrote:
>
> > * Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> >> > Seems kind of unlikely... What exact (.deb) versions of libpq and
> >> > Postgres are you using?
Andrew Klosterman <[EMAIL PROTECTED]> writes:
> (gdb) print *conn
> ...
> allow_ssl_try = 1 '\001', wait_ssl_try = 0 '\0', ssl = 0x806d1d0,
> peer = 0x807e430,
> ...
> *** glibc detected *** corrupted double-linked list: 0x0807e428 ***
Hm, it looks like the problem is associated with whatever
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > Another approach would be to have PQsetdbLogin build up a conninfo
> > string and pass that into connectOptions1 instead of calling
> > connectOptions1 with an empty string and then changing the values
> > afterwa
Stephen Frost <[EMAIL PROTECTED]> writes:
> Another approach would be to have PQsetdbLogin build up a conninfo
> string and pass that into connectOptions1 instead of calling
> connectOptions1 with an empty string and then changing the values
> afterwards. That'd probably be too large of a change t
* Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> On Tue, 14 Feb 2006, Stephen Frost wrote:
>
> > It's kind of a chicken-and-egg here because the backend decides what
> > authentication mechanism to ask for based off the username (at least in
> > part) through pg_hba.conf, so you can't find out the
* Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> Alright, I have built a system with the symbols left into the binaries.
[...]
> Again, it is showing a bad malloc in what appears to be some code using
> kerberos. But there's nothing in my setup that I can think of right now
> that should induce a
On Feb 13 04:01, Andrew Klosterman wrote:
> I threw in a pthread mutex around the code making the database connections
> for each of my threads. The problem is still there ("corrupted
> double-linked list").
> ...
> Program received signal SIGILL, Illegal instruction.
> [Switching to Thread 16384
--On Montag, Februar 13, 2006 21:25:30 -0500 Stephen Frost
<[EMAIL PROTECTED]> wrote:
* Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> Seems kind of unlikely... What exact (.deb) versions of libpq and
> Postgres are you using? You originally posted w/ 8.1.0 but perhaps on
> the client you
On Mon, 13 Feb 2006, Stephen Frost wrote:
> * Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> > (gdb) bt
> > #0 0x401c3851 in kill () from /lib/libc.so.6
> > #1 0x40139dd5 in EF_Abort () from /usr/lib/libefence.so.0
> > #2 0x40139823 in memalign () from /usr/lib/libefence.so.0
> > #3 0x401399ad
* Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> > Seems kind of unlikely... What exact (.deb) versions of libpq and
> > Postgres are you using? You originally posted w/ 8.1.0 but perhaps on
> > the client you had something more recent?
>
> Running "aptitude show X" where "X" is the package name
* Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> (gdb) bt
> #0 0x401c3851 in kill () from /lib/libc.so.6
> #1 0x40139dd5 in EF_Abort () from /usr/lib/libefence.so.0
> #2 0x40139823 in memalign () from /usr/lib/libefence.so.0
> #3 0x401399ad in malloc () from /usr/lib/libefence.so.0
> #4 0x4013
On Wed, 8 Feb 2006, Tom Lane wrote:
> "Andy Klosterman" <[EMAIL PROTECTED]> writes:
> > SPECULATION: Another possibility is that I misunderstand some aspect of
> > multi-threaded interactions with Postgres (I open uniquely named connections
> > to the DB for each thread of my test program). Maybe
On Mon, 13 Feb 2006, Tom Lane wrote:
> Andrew Klosterman <[EMAIL PROTECTED]> writes:
> > (gdb) bt
> > #0 0x401c3851 in kill () from /lib/libc.so.6
> > #1 0x40139dd5 in EF_Abort () from /usr/lib/libefence.so.0
> > #2 0x40139823 in memalign () from /usr/lib/libefence.so.0
> > #3 0x401399ad in ma
On Mon, 13 Feb 2006, Tom Lane wrote:
> Andrew Klosterman <[EMAIL PROTECTED]> writes:
> > I threw in a pthread mutex around the code making the database connections
> > for each of my threads. The problem is still there ("corrupted
> > double-linked list").
>
> > Even tuning things down and instru
Stephen Frost <[EMAIL PROTECTED]> writes:
> We do have debugging .debs- for some things. We don't have them for
> everything and unfortunately we don't yet have them for Postgres. I'll
> talk to Martin about building some though so that in the future it's
> easier to debug these problems.
Hmm.
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Andrew Klosterman <[EMAIL PROTECTED]> writes:
> > (gdb) bt
> > #0 0x401c3851 in kill () from /lib/libc.so.6
> > #1 0x40139dd5 in EF_Abort () from /usr/lib/libefence.so.0
> > #2 0x40139823 in memalign () from /usr/lib/libefence.so.0
> > #3 0x401399ad in ma
Andrew Klosterman <[EMAIL PROTECTED]> writes:
> (gdb) bt
> #0 0x401c3851 in kill () from /lib/libc.so.6
> #1 0x40139dd5 in EF_Abort () from /usr/lib/libefence.so.0
> #2 0x40139823 in memalign () from /usr/lib/libefence.so.0
> #3 0x401399ad in malloc () from /usr/lib/libefence.so.0
> #4 0x40139
Andrew Klosterman <[EMAIL PROTECTED]> writes:
> I threw in a pthread mutex around the code making the database connections
> for each of my threads. The problem is still there ("corrupted
> double-linked list").
> Even tuning things down and instructing my code to only run a single
> pthread mani
"Andy Klosterman" <[EMAIL PROTECTED]> writes:
> SPECULATION: Another possibility is that I misunderstand some aspect of
> multi-threaded interactions with Postgres (I open uniquely named connections
> to the DB for each thread of my test program). Maybe I need to have a
> "lock" around the code th
Andy Klosterman wrote:
> Before going into a full description and figuring out some example code for
> this situation, I'm fishing for interesting in tracking it down and fixing
> it (or not).
Whenever there is a bug that causes a crash, there is interest in
tracking it down and fixing it. Pleas
The following bug has been logged online:
Bug reference: 2246
Logged by: Andy Klosterman
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Debian testing: Linux nc3 2.4.27-2-386 #1 Wed Nov 30
21:38:51 JST 2005 i686 GNU/Linux
Description:Bad
29 matches
Mail list logo
