Re: BUG #13980: UNINITIALIZED READ

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: ranier_gyn(at)hotmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13980: UNINITIALIZED READ
Date: 2016-02-23 20:37:51
Message-ID: 20160223203751.GA372385@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

ranier_gyn(at)hotmail(dot)com wrote:

> Potential Error #1: UNINITIALIZED READ: reading 0x0012f3dc-0x0012f3e0 4
> byte(s)

> # 9 dbd_pgsql_open
> [c:\usr\src\dbd\postgresql\dbd_pgsql.c:190]
> #10 dbd_init [c:\usr\src\dbd\dbd.c:81]
> #11 sr_app_data_setup [c:\usr\src\sirius\app\app_dbd.c:241]
> #12 main [c:\usr\src\rcpdv\app.c:140]
> Note: @0:00:04.953 in thread 2700
> Note: instruction: cmp %ecx (%eax)

This bug, and the three HANDLE leaks you reported, appear to pertain to
DBD::Pg. It would be better to report this to the dbd-pg mailing list
https://metacpan.org/pod/DBD::Pg#AUTHORS or perhaps open a bug in
https://rt.cpan.org/Public/Dist/Display.html?Name=DBD-Pg
I advise including a test program that shows the problem.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2016-02-23 21:33:21 Re: BUG #13980: UNINITIALIZED READ
Previous Message Tom Lane 2016-02-23 15:38:08 Re: BUG #13979: Strange pg_stat_statements results with PREPARE/EXECUTE