V4MD conflict with debugger

Ruslan Zasukhin sunshine at public.kherson.ua
Fri Sep 8 00:58:04 CDT 2006


On 9/8/06 12:51 AM, "Christian - ChrisKatDev.com"
<christian at chriskatdev.com> wrote:

>>> on mKill me
>>>    _movie.trace = 0
>>>    if not (voidP (pDB)) then
>>>      pDB.close ()
>>>    end if
>>>    if not (voidP (pDBL)) then
>>>      pDBL.close ()
>>>    end if
>>>    pValentina.shutDown ()
>>>    pDB = void
>>>    pDBL = void
>>>    return void
>> 
>> Then try take a look into V4MD_Log file.
>> If you really see here calls to Valentina Shutdown.
>> Also you can see here which exactly function crashes.
>> Do you have crash log ?
> and non... not in this case :-(
> in other case, yes, but in this...

Hi Christian,

So there is no crash log ?
    this can happens in some c++ related issues.

I not remember: can you send us something that reproduce problem?
    I have see you regiter in Mantis.
    can you login now?

Also I still wit for db that show Vstudio related issue which you have point
on Valentina-studio list.

Please send us something ASAP. WE close to 2.4.2 release as I have mention
on Valentina beta list.

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]




More information about the Valentina mailing list