[linrad] Re: xlinrad 02.05. Problem solved(?)

[Robert McGwier <comcast.net; rwmcgwier@xxxxxxxxxxxxxxxx>]

Leif:

You will probably need to turn on the debug symbol generation and turn 
off optimizations and then you will be able to follow the progress.  You 
do not care that it is slow here,  you are attempting to find logic and 
other errors. 

gcc -g -O0  will turn off optimizations, insert debug symbols and you 
can then debug with gdb or valgrind.  Valgrind will take you to the very 
line (not sure about the assembly routines) of the problem.

Bob




leif@xxxxxxxxxx wrote:
> Hi Bob,
>
>   
> > Baahhh Humbug.  A programmer is someone who writes effective programs 
> > that accomplish a task.  You have certainly done that and you have 
> > produced now the version that will carry this work forward for a 
> > while.   Unfortunately, I do not believe valgrind is available under 
> > windows and it would be very difficult to make valgrind work because of 
> > the myriad differences between process/threads on windows and on all 
> > real operating systems.  ;-).
> >     
>
> What I mean is that I can not understand the manuals programmers
> write for each other. There is a whole language that I can not
> grasp and I just get confused. I have no problem reading the
> Intel definitions of the assembly language however. Those are
> written in normal technical language:-)
>
> I have spent some time trying to understand how to get more info
> out of valgrind. When valgrind points to an address I have no
> way of finding out what line in the C-code it corresponds to.
> The assembly routines are easy. I know what each line means and
> where it is located:-) The valgrind documentation is far too big
> like the gcc documentation. It is impossible for me to grasp:-( 
>
> Nearly all the Linrad code is identical for svgalib, X11 and Windows so
> I can find nearly everything with valgrind under X11. Is there
> a way to find the line numbers of the C-code? I know from the map
> where a routine starts. In an assembly program I can insert public labels
> reasonably close to where the problem is and then compute approximately
> where the error is and move the label. Within two or three iterations
> I find the offending statement. Not so under C. What is the proper way
> to handle this? 
>
>  
> 73
>
> Leif  /  SM5BSZ
>
> #############################################################
> This message is sent to you because you are subscribed to
>   the mailing list <linrad@xxxxxxxxxxxxxxxxxxxxx>.
> To unsubscribe, E-mail to: <linrad-off@xxxxxxxxxxxxxxxxxxxxx>
> To switch to the DIGEST mode, E-mail to <linrad-digest@xxxxxxxxxxxxxxxxxxxxx>
> To switch to the INDEX mode, E-mail to <linrad-index@xxxxxxxxxxxxxxxxxxxxx>
> Send administrative queries to  <linrad-request@xxxxxxxxxxxxxxxxxxxxx>
>
>
>   


--
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@xxxxxxxxxxxxxxxxxxxxx>.
To unsubscribe, E-mail to: <linrad-off@xxxxxxxxxxxxxxxxxxxxx>
To switch to the DIGEST mode, E-mail to <linrad-digest@xxxxxxxxxxxxxxxxxxxxx>
To switch to the INDEX mode, E-mail to <linrad-index@xxxxxxxxxxxxxxxxxxxxx>
Send administrative queries to  <linrad-request@xxxxxxxxxxxxxxxxxxxxx>


LINRADDARNIL