https://luisgo.pro/down/coredumps6.zip

Including citserver 

Centos 9, last version.

Specify please what you want to solve the problem. Do you want to have access to my server? Stack trace? How I obtain it?

Sat Sep 20 2025 18:08:00 UTC from IGnatius T Foobar Subject: Re: Concerning tha last two posts in Support Room.

Sorry again.

This night happened again. More coredumps. I updated the citadel. It installed and compiled a version but it remained the same version number. Did that attended my problem?

If not a send the new coredumps.

https://luisgo.pro/down/coredumps3.zip

I hope that you solved or are solving this problem.

Let see that if or not happen again.

Unfortunately, your core dumps are not useful to anyone because they are specific to your citserver binary.  I suppose if you include your citserver binary it might be useful, otherwise a stack trace is better.

In your case, we're just seeing so many weird things on your system that don't happen anywhere else.  It's difficult to pin down why.  I would strongly suggest that you give some consideration to moving to the containerized version of the Citadel system.  It is lovingly built for you in a carefully controlled environment.   Perhaps switch to the container version, and if necessary, do a ctdldump/ctdlload on your existing data.

And of course take lots of backups before doing anything.

Specify please what you want to solve the problem. Do you want to have access to my server? Stack trace? How I obtain it?

Stack trace would be far more helpful than what you are currently trying to do.   Since you seem to have the ability to produce core dumps, you are halfway there already.

After a core dump, do this:

gdb /usr/local/citadel/citserver core.xxxxxxxxx   (use the name of your core file)

The debugger will open, and show you where it crashed.   Now type:

thread apply all bt

And post the output.  it should show lots of filenames and line numbers.