[Harbour] Debugging c code

[April White]

You may recall my email from about a week ago about my Ubuntu machine.  I'm (re)installed 9.10 with the same results that it does not boot.  I do not know enough about linux / ubuntu to know whether it is a bug or a hardware failure.  Because the installation has no failures it says to me it is a bug not hardware.

Thank you!

April

p.s.  I've found a work around for the runtime error in the btree code, but I do not know 'why' is it happening.  More work to do.


> Subject: Re: [Harbour] Debugging c code
> From: harbour.01 at syenar.hu
> Date: Mon, 1 Feb 2010 16:10:00 +0100
> To: harbour at harbour-project.org
> 
> Hi April,
> 
> Under Ubuntu you can use valgrind to find out the exact locations 
> of leaked allocations. Check the debugging section in INSTALL.

> On 2010 Feb 1, at 04:00, April White wrote:
> 
> > When my C level code does not release memory, the fm statistics reports this but gives the public function though in some cases the allocation occured in a sub-function.  
> > 
> > Is there a macro I can use to identify this sub-function?  I could leave it in the code wrapped conditional code for debug only.  
> > 
> > April
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.harbour-project.org/pipermail/harbour/attachments/20100201/ad2aa40d/attachment.html