This is the case where a list element was created without using the DL_ macros but its deletion was attempted using DL_DELETE. Technically its a usage violation. In utlist DL lists have special rules that the macros maintain. Added an assertion to make this fail more 'deterministically' than by segfault. Not sure if this will go into the final release depending on whether Windows supports the assert.h header.
Side note: I rarely use SourceForge so please address bugs directly to me for best response (thanson@users.sourceforge.net).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Testcase
This is the case where a list element was created without using the DL_ macros but its deletion was attempted using DL_DELETE. Technically its a usage violation. In utlist DL lists have special rules that the macros maintain. Added an assertion to make this fail more 'deterministically' than by segfault. Not sure if this will go into the final release depending on whether Windows supports the assert.h header.
Side note: I rarely use SourceForge so please address bugs directly to me for best response (thanson@users.sourceforge.net).