Hello Bill,
Thanks for giving me some tips on how to get njamd running. I followed your
advice and still couldn't get it to run. Then I decided to uninstall the
njamd rpm and download the .tar.gz package from the web. compile and install
it and it run from the start. seems that the previous rpm install (default
by Redhat) is broken.
BTW, do you know of any good tutorial to use njamd? I don't find the njamd
manpage of much help. It details those env variables but they don't make
much sense to me.
Best,
David
----- Original Message -----
From: "Bill Crawford" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 18, 2002 6:27 AM
Subject: Re: Using njamd
On Sun, 17 Mar 2002, Bill Crawford wrote:
> You might want to add
>
> export NJAMD_ALLOW_FREE_0=1
You might also need NJAMD_NO_TRACE=1, there's a comment in the man
page that says:
NJAMD_NO_TRACE=1
When debugging programs that use libraries compiled with
optimization
greater than -O2 or with -fomit-frame-pointer, you must
disable tracing,
or NJAMD will segfault. This isn't really NJAMD's fault. Gcc
(see 'info
gcc') claims that if __builtin_return_address is unavailable
it will
just return NULL. Instead it segmentation faults. I've
notified the gcc
team, but received no response.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
