| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michal Novotný <michal(dot)novotny(at)greycortex(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Segmentation fault in libpq |
| Date: | 2017-07-02 19:12:22 |
| Message-ID: | 20170702191222.uk4hokc2iumzeenh@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hi,
On 2017-07-02 20:58:52 +0200, Michal Novotný wrote:
> thank you all for your advice. I've been investigating this a little more
> and finally it turned out it's not a bug in libpq although I got confused
> by going deep as several libpq functions. The bug was really on our side
> after trying to use connection pointer after calling PQfinish(). The code
> is pretty complex so it took some time to investigate however I would like
> to apologize for "blaming" libpq instead of our code.
Usually using a tool like valgrind is quite helpful to find issues like
that, because it'll show you the call-stack accessing the memory and
*also* the call-stack that lead to the memory being freed.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-07-02 19:39:31 | Re: BUG #14727: Inicial running of Postgres. |
| Previous Message | Michal Novotný | 2017-07-02 18:58:52 | Re: [HACKERS] Segmentation fault in libpq |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-07-02 20:40:49 | Re: Race-like failure in recovery/t/009_twophase.pl |
| Previous Message | Michal Novotný | 2017-07-02 18:58:52 | Re: [HACKERS] Segmentation fault in libpq |