| From: | Shachar Shemesh <psql(at)shemesh(dot)biz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: valgrind errors |
| Date: | 2004-04-22 16:18:35 |
| Message-ID: | 4087F05B.5060309@shemesh.biz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>Neil Conway <neilc(at)samurai(dot)com> writes:
>
>
>>Any thoughts on what could be causing these errors?
>>
>>
>
>I suspect valgrind is complaining because XLogInsert is memcpy'ing a
>struct that has allocation padding in it. Which of course is a bogus
>complaint ...
>
>
As far as I remember (couldn't find modern documentation on the matter)
Valgrind is resitant to this problem. When a block of memory is copied,
the initialized/uninitialized status is copied along. It only complains
when an actual operation is performed using uninitialized memory. This
was developed for the explicit reason of avoiding the problem you describe.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting
http://www.lingnu.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shachar Shemesh | 2004-04-22 16:25:00 | Re: valgrind errors |
| Previous Message | Shachar Shemesh | 2004-04-22 16:01:50 | Re: License question |