| Re: [AD] Problem with debug version and install_allegro autodetection macro |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2006-05-25, Grzegorz Adam Hankiewicz <gradha@xxxxxxxxxx> wrote:
> Working on Pyallegro I managed to get the python module linked
> against a different version of the C library. When install_allegro's
> library version autodetection kicked in I got a strange assert in
> debug mode. Here's the callstack:
...
>
> 83 int dll_v = _get_allegro_version(); /* This comes from the DLL. */
> (gdb) f 3
> #3 0xb7a36ee5 in get_executable_name (output=0xbfffebc0 "]", size=1024) at src/allegro.c:466
> 466 ASSERT(system_driver);
> (gdb) print system_driver
> $1 = (SYSTEM_DRIVER *) 0x0
>
> Funny thing is I r'grepped for "version mismatch" and couldn't
> find it anywhere...
Hi, this was a bug in 4.2.0. Programs compiled with 4.2.0 but running
with 4.2.1 (SVN) should not crash now. I'm not sure about debug mode,
but we don't really support binary compatibility for debug mode anyway.
Peter