B
BruceVx
Guest
Hello, To begin with, this is another post on a troublesome error. I apologise for the multiple postings, but I believe I'm getting closer to the problem.
I have an MFC application that uses MIDI functions under winmm.lib. Device opening starts with the following statements:
UINT numdevs;
numdevs = midiOutGetNumDevs();
The overall application runs OK in release, but when I run it in debug, the debugger flags an exception on calling midiOutGetNumDevs(). If I break from debugging, here is the information that appears:
==============================================
MIDIprog has triggered a breakpoint.
Exception thrown at 0x774414C8C (ntdll.dll) in MIDIprog:0xC0000005.
Access violation reading 0x01E729D2.
If I select Proceed, the debugger just flags the same error repeatedly.
==============================================
Since there appear to be no problems in release, the only difficulty this is causing - aside from an uncomfortable feeling - is that it prevents me using debug mode to track down other bugs. There is nothing particularly applicable that I can find with MSDN or Google, and that function doesn't return error codes.
I've already taken up peoples time on this one, but if there is a known reason for this situation I'd appreciate if someone could let me know. Thanks in advance.
bv
Continue reading...
I have an MFC application that uses MIDI functions under winmm.lib. Device opening starts with the following statements:
UINT numdevs;
numdevs = midiOutGetNumDevs();
The overall application runs OK in release, but when I run it in debug, the debugger flags an exception on calling midiOutGetNumDevs(). If I break from debugging, here is the information that appears:
==============================================
MIDIprog has triggered a breakpoint.
Exception thrown at 0x774414C8C (ntdll.dll) in MIDIprog:0xC0000005.
Access violation reading 0x01E729D2.
If I select Proceed, the debugger just flags the same error repeatedly.
==============================================
Since there appear to be no problems in release, the only difficulty this is causing - aside from an uncomfortable feeling - is that it prevents me using debug mode to track down other bugs. There is nothing particularly applicable that I can find with MSDN or Google, and that function doesn't return error codes.
I've already taken up peoples time on this one, but if there is a known reason for this situation I'd appreciate if someone could let me know. Thanks in advance.
bv
Continue reading...