Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Tracking down a certain debug error...

  • 04-08-2006 7:03pm
    #1
    cornbb
    Registered Users, Registered Users 2 Posts: 6,790 ✭✭✭


    Hi everyone,

    I'm hoping that someone with a bit more C++ development experience than myself can help out here.

    I'm using Visual Studio 6.0 to develop a DLL that will function as an audio effects processing plug-in (VST format, in case anyone is familiar with it). I'm using an SDK for the development, this includes a number of sample VC++ 6 projects which build and run without any trouble.

    The problem is this: when I try to load my plug-in into a host application, I get an debug error. It varies depending on the host I use, but looks something like this:
    Debug Error!

    Program: C:...cubasesx.exe

    DAMAGE: after Normal block (#46) at 0x.....

    Abort/Retry/Fail

    I'm led to believe this is due to a memory corruption/overrun of some sort. Problem is, my debugger won't give me any clues as to what is going on... Does anyone have any advice on what strategies I could use to track this bug down, apart from going through my thousands of lines of code, line by line...

    Thanks!


Comments

  • #2
    Martyr
    Closed Accounts Posts: 1,567 ✭✭✭Martyr


    what debugger are you using?
    does the VST crash without a debugger being present?
    what version of cubasesx are you using?
    sx3 is protected by syncrosoft dongle software
    previous versions had copy protection mechanisms also to prevent debugging.


  • #3
    cornbb
    Registered Users, Registered Users 2 Posts: 6,790 ✭✭✭cornbb


    Thanks for the reply - I actually got the problem fixed at 4am last night. It was caused by the string conversion functions supplied with the SDK (apparently 2.4, the version I'm using, is a piece of sh*t)

    I'm using the Visual C++ 6.0 debugger and SX2 - yes, it did crash without the debugger. Up until now, I was using Tobybear Minihost, an excellent free VST host, to do all of my debugging.


Advertisement