Bug#2471: aXe core dumps straight away
[about axe core dumping with Xaw3d installed,
and working OK without it]
> Is this a axe bug or a Xaw3d bug?
I've tried to determine this (as xaw3d maintainer), but failed.
When I start axe with "-noserver", it segfaults in AxeEditor.c:4059,
window = XtVaCreatePopupShell(name, axeWindowWidgetClass, parent,
XtNfile, file,
NULL);
The arguments to XtVaCreatePopupShell seem reasonable (parent seems ok,
name is a valid string, file is a null pointer, but making it point to
a string makes no difference).
So, probably something in the axeWindowWidget what doesn't like Xaw3d.
I'll try to look into this widget when I have some time, but I guess
for now we should make our packages conflict with each other.
(BTW, not giving the option "-noserver" makes it segfault in the
XtAppMainLoop, making debugging harder).
>
> Michael Meskes writes:
> >
> > Andrew Howell writes:
> > > open("/usr/X11R6/lib/Xaw3d/libXaw.so.6.0", O_RDONLY) = 3
> >
> > Here's the problem I think. Axe is compiled to use Xaw not Xaw3d. I do not
> > even have Xaw3d on my system. So I assume you installed that locally.
But all other programmes I know of work with either Xaw or Xaw3d.
SHOULD make no difference, unless there's a bug in either of them.
> Andrew Howell andrew@it.com.au
> Perth, Western Australia howellaa@cs.curtin.edu.au
--
joost witteveen
joost@rulcmc.leidenuniv.nl
joostje@dds.hacktic.nl
--
There's no substitute for reading README's.
(except for using Debian, and typing "dpkg -i package.deb").
Reply to: