On Mon, Jun 03, 2019 at 09:43:11AM +0000, jpayanides@prosodie.com wrote:

Hello Ondřej,

Hi Jean-Philippe,

sorry to answer so late, I was off (sick).

Answering your questions:

I didn't try to reproduce the crash on a different system.

this will be the easiest way to get more information both on whether the crash might be coming from another of the system and, with newer tools, more about the crash itself.

What is the goal of installing an new version of gdb on my system ? I am not sure it will be easy to proceed.

From what you have provided, the version of gdb you have used seems to

have issues debugging this program, a newer tool might be able to do a better job (or you can try remote debugging with gdbserver). But if you can, trying to reproduce this on a different (newer) system should be a priority.

Following your advise, I have corrected the chain configuration with removing mode=self, but it didn't change nothing regarding the crash.

do you think it could be possible that the glibc contains bugs resulting that crash?

Hard to tell, your system is ancient and I have no idea how stable any part of it was.

I do not know what to do. Would it be relevant to upgrade the OS?

If you can upgrade the system at all, please do so, it has been about 12 years since Debian Etch was released and many things have happened since.

Regards,