Leif Asbrink wrote:
Hi Ramiro,
I have just downloaded Linrad-02.05 and I can go a little bit further
but It crashes again. This is the sequence of commands
I press S
I choose 1 font size.
I choose N to allow swapping.
I press A for weak signal CW
I choose device 63 /dev/dsp
I choose
Hello again.
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.
[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
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
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
Leif Asbrink wrote:
Hello Ramiro,
xlinrad crashes under Debian Sarge and shows the following Segmentation
Fault debbuged with gdb. I send it to you just in case it gives you some
clues. Is the 890=0x37A port a parallel port register? What is it used
for under Linrad?
Linrad uses the
Linrad uses the parallel port to control the WSE hardware.
For this reason one has to run Linrad as root, something
that also makes it easier to use svgalib.
Thanks, I shoud have read the manual.
If you want to disable the parallel port reads and writes,
set VALGRIND TRUE in vernr.h
Leif Asbrink wrote:
Hi All,
Known bugs are now corrected:-)
Hello Leif,
-- Xlinrad 02.07 works very well, no crashes, no segfaults, no problems
at all.
-- sgvalib linrad 02.07 works for some while and segfaults:
svgalib: signal 4: Illegal instruction received
On 4/21/06, Leif Asbrink [EMAIL PROTECTED] wrote:
Hi Ramiro,
-- sgvalib linrad 02.07 works for some while and segfaults:
svgalib: signal 4: Illegal instruction received
svgalib: signal 11: Segmentation fault received
I have not been able to reproduce. I have tried Sarge
Leif Asbrink wrote:
Hi Ramiro,
-- sgvalib linrad 02.07 works for some while and segfaults:
svgalib: signal 4: Illegal instruction received
svgalib: signal 11: Segmentation fault received
I have not been able to reproduce. I have tried Sarge
with the 2.6.8 kernel but it just
Leif Asbrink wrote:
Hello Ramiro,
I also have not been able to reproduce the bug on my desktop computer.
The bug shows only on my laptop computer.
I have been trying to run Linrad under gdb and valgrind but any of them
allows it. I cant run Linrad within them.
This seems odd, I thought
Hello again!
I have just compiled svgalib 1.9.24 and linrad works great using
NO_HELPER mode! No crashes, it works just fine.
Can we conclude it was a svgalib bug?
73, Ramiro, EA1ABZ.
#
This message is sent to you because you are
Leif Asbrink wrote:
Hi All,
This is only for those of you who run Debian Etch.
Running apt-get upgrade may make your system
impossible to boot. For a while I thought my
hard disk was corrupted because the last thing I had
done before rebooting was to try the SDR-14 which
did not work (2.14
14 matches
Mail list logo
