Crash with module with incompatible ABI #102

New Issue

2026-10-05T03:59:04+02:00

adam commented

2026-10-05 03:59:04 +02:00

On devel/git versions the version number is not changed, but ABI is changing. So if someone uses an external module and didn't recompile it, ZNC crashes.
It happens even on start, when ZNC does GetAvailMods() at the beginning to check if it's installed properly.

Need some other way to ensure the same ABI, not just version number.

On devel/git versions the version number is not changed, but ABI is changing. So if someone uses an external module and didn't recompile it, ZNC crashes. It happens even on start, when ZNC does GetAvailMods() at the beginning to check if it's installed properly. Need some other way to ensure the same ABI, not just version number. ##

adam closed this issue

2026-10-05 03:59:04 +02:00

adam commented

2026-10-05 03:59:05 +02:00

Perhaps we can use the last commit hash instead of a version number?

In the final release we can use a version number, the configure script can have the "ABI number", so the nightly build can place it there.

Perhaps we can use the last commit hash instead of a version number? In the final release we can use a version number, the configure script can have the "ABI number", so the nightly build can place it there.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#102