Re: [REQADM-Users-L] reqadm-create segfaults (Linux)

[Steve W. <st...@al...>]

In message <200...@tt...>, Matthew White writes:
>Trying to get 1.3 working on a debian 3.0 box.  I managed to get
>everything complied and installed.  When I try to create tickets via email
>(reqadm-create -m) or via the X client I get segfaults.

Interesting.  I don't have debian here to test with.  1.3 does work
on FreeBSD 4.8, though, which is a very similar set of GNU compilers
and libs, etc.  Did you get a coredump file?  If you feel energetic,
you can try to bring that up in gdb or ddd and see where the offending
line seems to be.

>The tickets do make it into the system but somewhere along the line it
>dumps core.  Along with this, I see the error mesasge "REQADM Server
>Error:  Unable to look up token".  I haven't been able to determine
>which token REQADM is unable to look up.

Ah, actually this may be the source of the problem.  If you are missing
a field in reqadm.conf, that will make REQADM segfault, unfortunately.
I'd check your reqadm.conf file vs. the reqadm.conf.sample supplied
with REQADM and make sure there are no fields missing (most can be
defined to no value as in:

XYZQ=

rather than deleting the line altogether.  The coredump file should help
here, if you can see the value of u on line 1258 right before the
segfault.  That'll be a 32-bit number equivalent to the four-byte
token name.  If you start reqadm-create with the -zdebug option, you
should see a "$<number>" (e.g., "$4A593630") command prior to the 
segfault.  That would be the number you're looking for as well
(in hex).