I do not undertand why this happens, because I chose N to the question:
use mlockall to prevent swapping ? (Y/N) - N
This is a trivial bug. There should have been a test if(ui.memloc==0)
Ok. The xz() function has been a very efective way of finding where the
crash occured. Thanks for
Hi Ramiro,
I have tested xLinrad 02.05 on both very different machines. A 1.86 GHz
1GB RAM Pentium Centrino laptop and a 1.2 GHz AMD Athlon 256 MB desktop
computer. I get an strange CPU usage increase up to 100 % before real
operation, in the parameter selection screen.
I think this is
[EMAIL PROTECTED] wrote:
Hi Ramiro,
The way I locate this kind of errors is th change DUMPFILE,
now in vernr.h, to 1.
Hello Leif,
I have done the debugging you suggested.
After some compilation and xz iterations, I have found that the
funcion that completly crashes my computer is
Hi Leif,
Forgot to post the debugging xz:
int lir_lock_mem(void)
{
int i,k;
xz(lir_lock_mem_1);
i= mlockall(MCL_CURRENT);
xz(lir_lock_mem_2);
if(i==0)return 0;
k=errno;
munlockall();
errno=k;
return i;
}
More information about the mlockall issue.
This dirty code modification
Hi Ramiro,
After some compilation and xz iterations, I have found that the
funcion that completly crashes my computer is mlockall(), called from
function lir_lock_mem() in lsys.c.
lir_lock_mem() is called from main() in lmain.c
The call to mlockall() never returns and crashes the
Thank you for getting there before I had a chance. I love this tool.
It has saved my technical ife on three occassions in the last year.
Bob
Ramiro Aceves wrote:
Hello Leif and others.
I have run xlinrad under valgrind. I never had heard about this
tool. Thanks to Bob for pointing in
Robert McGwier wrote:
Thank you for getting there before I had a chance. I love this tool.
It has saved my technical ife on three occassions in the last year.
Bob
Hello Bob,
I had heard about gdb but never heard valgrind. You were the first
person that let me know that valgrind
Hi, Leif,
Thanks for the reply! OK on CPU overload being the likely culprit.
Just for documentation, I am running on the machine used for the tests I
have reported:
3.2 GHz P4
1.5 GB RAM
Debian Sarge
Kernel 2.6.13
Xfree86 4.3.0.dfsg.1-14_i386
ati x driver
PCI Express ATI RV370 (Radeon X300
Hi, Leif,
Just a quick final note before I run off to work:
THe previous note of course referred to xLinrad, as does this one.
I went back to xLinrad and found that:
1st FFT storage time was 1 second. I left it there
2nd FFT storage time was 5 seconds. I left it there
Baseband storage time
Hi, Leif,
THis is just some 'user feedback' from 1.37 and 2.05 ;)
Windows:
Linrad-02.05 is working fine so far. I haven't made it fail under windows.
Linux:
LInrad 01.37 seems to work fine here at home. I haven't put it thru its
paces at Hilltop yet.
LInrad-02.05 works fine under svgalib.
10 matches
Mail list logo
