Error message caused into to the microstation v8i s3

Do you supply an email address & description of the problem in the designated area and submit to Bentley?

I see that dialog often during development.  It is caused by an MDL program, often through a memory leak.

Since you have posted no code, we can't provide any further diagnosis.

Unknown said:

We modify the content of components as Text component, combo box component...

It's not clear what you mean.  Are you referring to dialog items, or is 'Text component' a MicroStation text element?

Since you're using MDL, have you tried using the MDL debugger?

Yes, I did

Not sure, if the submission would result in any response (at least I never got any response). But beside this, that screenshot is the most unvalueable thing you might provide for any error in this forum. If you work extensive with UStn, you should have seen that thing from time to time.

Unknown said:

These bugs occur as a message error when we modify the content of components as Text component, combo box component...

Not sure what components you are talking of, nor how you modify them (it might be usefull to show us some pieces of code here). If you talk of a 'message error' do you mean that dialog from the screenshot, or do you receive anything else ?

Is the error reproduceable ? Have you tried to debug things to break it down to some procedure or piece of code ? Is the error related to some kind of string handling ? You even haven't told us, how you are creating your application. Is it a Native one or a 'classic mdl' ? Have you used to recompile it with the appropriate sdk ? How was it compiled at all ? While you are almost able to run applications that where build for earlier Versions of MicroStation, there is no guarantee, that they continue to work without a recompilation.

A number of things to think about, and provide additional information that might enable us to help you.

Regards Michael

Unknown said:

Yes, I did

Hmm.  Is that enigmatic or simply terse?

Could you Zip the entire MicroStation Temp directory and either post the .zip here for review, or private message me the necessary files?  Once received I can review the ExceptionHistory events and the associated Exception.log and Minidump.dmp file(s) to try to identify the source of the problem.

   MicroStation key-in to open Windows Explorer in the user configured MicroStation Temp directory

   1. MicroStation key-in:  $ % explorer $(MS_TMP)

   2. Zip and send the entire MicroStation Temp directory (e.g. _dMmaOKrOBZUzT62asU91Q) and submit for review

HTH,

Bob

@ Jon Summers

this was my answer to mwlong's question

"Do you supply an email address & description of the problem in the designated area and submit to Bentley?"

Hello Every body

First, I’d like to thank you for your fast interaction.

I’m going to give more details about the problem that we have and about our solution.

Dkmètre is a native mdl application that is developed and compiled with the IDE visual studio 2005, the SDK which is used is “mssdk08110517en”.  When we updated our microstation v8i from series 2 to series 3 we did not install a new SDK.

The dialog box message error that we get is due to some actions as modifying the content of some text component or some combo box component (but not all the text and combo box component of the solution). So, in order to understand the piece of code that launch  this message error, I debugged and I found that it is due to the mdl function call:

mdlView_setLevelDisplay( dgnModeleRef, noVue, idNiveau, FALSE );

This screenshot above mentions the value of the parameters passed to the mdl function.

For your questions, I think I have answered some of it in my post

@ Jon Summers : have you tried using the MDL debugger?

No I didn’t, I’d like to know if I can use the mdl debugger with the visual studio IDE

@Michael Stark : Do you mean that dialog from the screenshot?

Yes it is

Is the error related to some kind of string handling?

No, I don’t think so.

@  Robert Hook [Bentley] 

I did not understand which files exactly do you need and where can I find them? 

Beside the fact, that the given levelId (idNiveau) is strange (never seen such a large one), a DgnModelRefP of 0 is definitively not correct. I'm not sure if this function should handle a NULL-reference, but no matter, it is wrong to give a NULL value for a model ref. How do you retrieve this DgnModelRefP ? If this works in previous versions, than even by mistake.

Unknown said:

I’d like to know if I can use the mdl debugger with the visual studio IDE

If you have a native-code application, then use the Viz Studio debugger.  You need to attach MicroStation as the host process (ustation.exe) for your DLL.

Unknown said:

mdlView_setLevelDisplay( dgnModeleRef, noVue, idNiveau, FALSE )

Your screenshot shows that the dgnModelRef pointer value is 0 (NULL).  Try using a valid model reference (e.g. ACTIVEMODEL).