[epiar-devel] unhandled exception in xtree

[Maoserr]

I think it's highly likely that the problem only shows up in debug mode  
because debug mode does a stricter checking of memory error than release  
mode. The NOTFOUND should be right, those variables are used to detect  
existing dependencies (which you shouldn't have).  You should probably  
remove all the duplicate libraries from your path and re-generate if you  
have problems with linking.

It's unfortunate that most people here use GCC without any kind of memory  
checker, because in my experience GCC doesn't do much in terms of memory  
error checking and only segfaults on unavoidable errors.  It is common to  
see buffer overflow and use of freed memory problems go undetected in GCC  
where visual studio would immediately raise an exception.

I would try to solve the source of the debug errors and try not to develop  
in release mode. Of course it might also be some rare problem, I had a  
heap corruption error earlier but went away once I did a chkdsk, but I  
think that's unlikely.

Arke might have more insight into this.

On Mon, 09 Aug 2010 05:20:53 -0400, Димитър Станчев <plural at abv.bg> wrote:

>  I have the very same problem but only in debug mode. In release it runs  
> properly(haven`t tried the others) Was thinking it didn`t configure  
> properly cause I have some duplicate libraries installed and some of the  
> viriables say ...-NOTFOUND.
>
> Was wandering, does cmake configure the libraries too or we have to run  
> their own cmake scripts?
>
>
>
>  >-------- Оригинално писмо --------
>  >От:  Maoserr
>  >Относно: Re: [epiar-devel] unhandled exception in xtree
>  >До: epiar-devel at epiar.net
>  >Изпратено на: Понеделник, 2010, Август 9 07:54:00 EEST
>
>  >that's probably not the source of the error, probably a memory error,  
> try
>  >stepping around, either that or you have a really messed up visual  
> studio
>  >environment
>  >
>  >On Sun, 08 Aug 2010 21:08:15 -0400, Doug Mirro
>  >wrote:
>  >
>  >> Unhandled exception at 0x011a9501 in Epiar_debug.exe: 0xC0000005:  
> Access
>  >> violation reading location 0x00000018.
>  >>
>  >> this pops up immediately when i try to run after rebuilding the  
> solution
>  >> in debug.  it occurs in xtree, which is part of visual studio
>  >>
>  >>                             _Nodeptr&amp; _Root() const
>  >>                                      {    // return root of  
> nonmutable
>  >> tree
>  >> code breaks here  ->     return (_Parent(_Myhead));
>  >
>  >
>  >_______________________________________________
>  >epiar-devel mailing list
>  >epiar-devel at epiar.net
>  >http://epiar.net/mailman/listinfo/epiar-devel
>  >