Horton

Re: Non-reproducible AIO failure

Andres Freund <andres@anarazel.de>

View thread
From: Andres Freund <andres@anarazel.de>
To: Konstantin Knizhnik <knizhnik@garret.ru>
Cc: Thomas Munro <thomas.munro@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-06-10T20:09:53Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. aio: Stop using enum bitfields due to bad code generation

  2. amcheck: Fix posting tree checks in gin_index_check()

  3. aio: Add missing memory barrier when waiting for IO handle

Hi,

On 2025-06-10 21:09:18 +0300, Konstantin Knizhnik wrote:
> 
> On 10/06/2025 8:41 pm, Andres Freund wrote:
> > I was able to reproduce it with gcc, too.
> > I've reproduced it without that bitfield, unfortunately :(.

> But also only at MacOS?

Correct.


> I wonder if it is possible to set hardware watchpoint fro program itself
> (not using gdb)? I.e. using ptrace?
> Looks like it is not possible to debug yourself:
> https://stackoverflow.com/questions/64321402/adding-a-watchpoint-in-the-current-process-not-in-gdb-not-for-debugging
> 
> but it is possible to fork process.
> In theory it certainly should be possible - gdb is normal process, so at
> least we can implement our mini-gdb.
> But not sure how complex it will be.

If this were on intel, I would try to use intel-pt to get the execution trace
for the recent past at the time of the assertion failure, but it's not
intel...


FWIW, in all the incidents I looked at the actual read-in buffers are valid,
so it's not like the IO did not occur or such.


Greetings,

Andres Freund