[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Wed, 2004-07-21 at 15:27 +0200, Evert Glebbeek wrote:
> On Wednesday 21 July 2004 15:09, Elias Pschernig wrote:
> > > I've attached a patch that should fix this issue, but it seems the
> > > problem is really in get_config_string, which shouldn't be returning
> > > NULL, AFAICT.
> > >
> >
> > Yes, don't apply such a patch. Check if it really returns NULL, and if
> > it does, check why. Maybe there's a stray config entry, or else a bug in
> > get_config_string we should fix.
>
> Apparently, it doesn't, as Chris's patch seems to make no difference for
> me...
> I'm trying to figure out where exactly the Allegro call comes from that
> causes the crash, but I'm having trouble getting gdb to give me a useful
> traceback (I probably need to rebuild everything at maximum debugging
> level). Oddly enough, any printf() statements I include in the code don't
> seem to be executed...
> I'll continue to investigate for now, but I may not have time to wrap it up
> today.
Try: "make uninstall-libs"
My suspection is, you have some 4.1.14 modules lying around, which
Allegro picks up (even when statically linked against the CVS version).
I already suggested once to change this behavior, and have a version
compiled with --disable-modules never use any modules at all, not just
not compiled them. Maybe we should reconsider this.
--
Elias Pschernig