winMM mscoree combo problems


Eric T

Hello friends, I'm in charge of some pure VC++ code but we're adding new
features using managed C++ (7.1). On two of three developer machines the
execution of this code has become impossible recently -- we don't know what
changed. Depending on my lib files list order I get different errors. If I
have winmm first, I get this in Windbg since I can't even get to the entry
point [main()] -- this same error happened in VC6 before I ported the pure
C++ to 7.1:

(100c.1070): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000001 ebx=7c810119 ecx=7c917304 edx=00240608 esi=00000010
eip=76b439a6 esp=0012f1c4 ebp=0012f1d8 iopl=0 nv up ei pl nz na pe
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000
76b439a6 ?? ???

If I put winmm.lib after the DLL which is written in managed C++, then I can
single-step to the point where the first function of the managed DLL is
called, at which point I get:
[WinDBG dump, since it shows more:]
(17a8.e04): Break instruction exception - code 80000003 (first chance)
eax=00241eb4 ebx=7ffdd000 ecx=00000003 edx=00000008 esi=00241f48
eip=7c901230 esp=0012fb20 ebp=0012fc94 iopl=0 nv up ei pl nz na pe
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntdll.dll -
7c901230 cc int 3

It often will take the entire VS7.1 down with it. On one of the three
development machines things work fine.
I'm totally stumped -- if anybody has any ideas in which direction to turn,
please advise.




Eric T

Further to this, when I commented all the winMM dependent stuff out, I still
had the problem as described in the second half. I could single-step as far
as the first managed function, and no further. When trying to debug it from
the managed DLL's perspective, it crashed VS7.1.

Eric T said:
Hello friends, I'm in charge of some pure VC++ code but we're adding new



Gary Chang[MSFT]

Hi Eric,

I am afraid we don't analyze the customer's dump info in the newsgroup,
this is beyond our newsgroup's support boundary. Since this problem only
occurs in two of your developers' machine, this issue may need more
extensive debug work to do. In this scenario, if you need a solution from
us to work around this problem, it is better for you if one of our PSS
support engineers could work with you. They will have more resources
available to help you efficiently tackle this issue. This may require you
to submit a support incident in Microsoft PSS (Product Support Service). As
a MSDN subscriber, you have two free support incidents.

By the way, if the problem is confirmed by Microsoft PSS as a product
issue, PSS won't charge money. Every MSDN subscriber has two free support
incidents. You could use one of them to contact Microsoft PSS. So you don't
need to pay money yet. If the issue is a product issue, you still have two
free support incidents.

For your reference, I have attached steps to contact Microsoft PSS here:
You can contact Microsoft Product Support directly to discuss additional
support options you may have available, by contacting us at 1-(800)936-5800
or by choosing one of the options listed at:;en-us;offer

Thanks for your understanding.

Best regards,

Gary Chang
Microsoft Online Community Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question