[linrad] Re: Linrad 02.06a
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 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. Oh my good, I was running xlinrad as a normal user, what a mistake. It works as root! I asumed that root was neccesary only for svgalib :-( Sorry for that I will elaborate later, I must go work know. Thanks!! and Sorry!!! EA1ABZ. # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Memory leakage.
Leif I cant speak as an accomplished programmer, having only done simple projects in C++ Still the code seems to be part of a routine. It looks like cross_cursor is an object of class XCreateFontCursor Maybe this is not being destroyed after use? I havent the faintest how you would find the class code for this X11 on my machine appears to be all C, though I cant locate source - I have just loaded Mandrake from a CD No doubt there are more accomplished programmers who could advise.. Richard Leif Asbrink wrote: Hello Richard, Lost memory is allocated when an object in C++ is created , but not released when the object is destroyed. This is usually performed by the destructor for the class if the class has been written properly. ??? I have seen similar text before, but it does not tell me anything at all. I have for example this problem. Only four simple statements: xdis = XOpenDisplay(:0); cross_cursor = XCreateFontCursor(xdis, XC_diamond_cross); XFreeCursor(xdis, cross_cursor); XCloseDisplay(xdis); return 0; If I comment out the second and the third statement all is ok, but with both of them in place I get this report from valgrind: ==9031== LEAK SUMMARY: ==9031==definitely lost: 8 bytes in 1 blocks. ==9031==indirectly lost: 104 bytes in 4 blocks. This results in increasing useless RAM utilization and eventually disk swapping, slowing everything down. How can I detect whether it happened? (hope I am not telling you things you already know.. :) ) You told things I kind of heard about but that I do not understand how to deal with. Did I make a mistake in the example above or is X11 not quite ok yet? Do you know? Using pthreads is much worse.. 73 Leif # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED] # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Memory leakage
Leif Asbrink wrote: If I can assume that lost memory is reclaimed by the os at program exit or at some suitable time afterwords (daily?) I can just forget the whole issue:-) A few KB at program strart or mode change is not a big problem. If you are growing by 1KB per minute or something ... well that's a different story! Why bother about small memory leaks as long as they are cleaned up at program exit :-) It's a question of elegance. Kind of like dressing the cables behind your operating desk. When all your features have been added, all the other bugs are fixed, perhaps you can return to this issue and clean it up. For now, set it aside and sleep easy! -Joe # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Memory leakage.
There is (usually) a destructor Richard, Please note that X, like most Unix software that has been around for any length of time, is written in C, not C++. Consequently, one often has to explicitly call some sort of close() function to clean up resources rather than relying on a destructor. -Joe KM1P # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: xlinrad 02.06a / error 23855
Hi Pierre, If I enter Y ( DA STOP/START [1] in par_userint ) everything works fine. If I enter N ( DA STOP/START [0] in par_userint ) xlinrad issues an error message 23855 when a new signal is selected . When something goes wrong with the device drivers (which was not uncommon at all in the past) Linrad calls err_restart_da(int errcod), a routine that tries to close and reopen the output device. This routine has been incorrect for some time now because of a silly mistake of mine but I have not noticed and no one else has told me about it. The last line: if(ioctl(audio_out,SNDCTL_DSP_GETOSPACE, da_info) != -1)lirerr(errcod); should be like this: if(ioctl(audio_out,SNDCTL_DSP_GETOSPACE, da_info) == -1)lirerr(errcod); What is more interesting is why does the output routine lir_dawrite hang to issue the call to restart in one case but not the other. I do not know the answer but I made some little changes to lir_empty_da_device_buffer() that will show up in Linrad-02.07 and that possibly eliminate the call to the err_restart routine. 73 Leif / SM5BSZ # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: Linrad 02.06a
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 Ok. I have now downloaded Sarge and it does not support my Delta44 so I have to use the SCSI card in RDWR mode. This made me discover a bug in 06a (and a few earlier ones): Linrad closes the device before it stopped both input and output which causes segfaults. It has nothing to do with Sarge, I noticed because Sarge made me try RDWR which I had not done for quite some time. Interesting. At least your 12 hours download worth the effort! RDWR is the mode I use! Ramiro, since your hardware does not need the parallel port, you should make a users hwaredriver that does not offend your preferred mode of operation. That is another way to disable parallel port access. Linrad 02-07 will (hopefully) give an error message rather than a segfault. Thank you very much Leif for the suggestions. I hope one day I can understand how Linrad works internally. Anyway, I am learning C reading your code under Vim editor and it is a very good learning experience. This editor is really efficient for jumping between function calls. ;-) 73 Ramiro. EA1ABZ. 73 Leif # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] New linrad data contribution by K0IK
Hello All, Brian, K0IK did submit his Linrad installation data on a Windows XP PRO SP2 platform, ver. 2.06a http://www.nitehawk.com/linrad_dat/ K0IK is using as analog front-end the very popular Softrock-40 SDR Kit. ( Under USD 25.- ) See: http://www.amqrp.org/kits/softrock40/ http://www.amqrp.org/kits/softrock40/version5.html For more details see also Yahoo Group Softrock Thanks so much, Brian. 73 Rein W6/PA0ZN # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
[linrad] Re: New linrad data contribution by K0IK
Softrock 7.0 looks particularly good as a 10 meter IF. It is basically the Giancarlo Moda H mode mixer. I have one finished. I will publish my number on it soon using D44 and Linrad to do the measurements. Bob Rein A. Smit wrote: Hello All, Brian, K0IK did submit his Linrad installation data on a Windows XP PRO SP2 platform, ver. 2.06a http://www.nitehawk.com/linrad_dat/ K0IK is using as analog front-end the very popular Softrock-40 SDR Kit. ( Under USD 25.- ) See: http://www.amqrp.org/kits/softrock40/ http://www.amqrp.org/kits/softrock40/version5.html For more details see also Yahoo Group Softrock Thanks so much, Brian. 73 Rein W6/PA0ZN # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED] -- AMSAT VP Engineering. Member: ARRL, AMSAT-DL, TAPR, Packrats, NJQRP/AMQRP, QRP ARCI, QCWA, FRC. ARRL SDR Wrk Grp Chairman Laziness is the number one inspiration for ingenuity. Guilty as charged! # This message is sent to you because you are subscribed to the mailing list linrad@antennspecialisten.se. To unsubscribe, E-mail to: [EMAIL PROTECTED] To switch to the DIGEST mode, E-mail to [EMAIL PROTECTED] To switch to the INDEX mode, E-mail to [EMAIL PROTECTED] Send administrative queries to [EMAIL PROTECTED]
