generate sequence diagrams from debugger

[Mr. Sanders]

Hello,

we have a generic architecture, where the needed components are loaded at runtime via configuration files. So the components are of course not listed in the assembly manifest.

Now we want to create some sequence diagrams to track the method calls in some of this dynamic components.

So we configured debug scripts at the package  to attach to the running process.

When all dynamic components are loaded we try to start the debugger and set breakpoints.

When we set the breakpoints, the breakpoints always have the question mark (not attached!). When we open the module tab in the debug workbench, our dynamic modules are not listed.

When we open an external process explorer, we see our modules loaded, and when debugging  in devstudio everything is fine.

Is this a problem of the debug workbench, because of the missing assembly manifest entries?

Is there some other magic trick?

We have c#.net assemblies.

Any hints would be helpfull.
Thank you.

[Vinx]

Hi MIZD,

I'm pretty new on this issue so my way might not be the best one, but at least I've got a way to debug:

- Create a Package Build Script (Shift + F12, Add)
- Insert name and directory of the script
- From the Debug tab select "attach to process"
- Since the Ok button is deactivated, add a whitespace in the text box of the Build tab (this can be removed after clicking Ok and Edit)
- Open the source from EA and add breakpoint
- Press F6 (Debug and Run)

Regards,

V.

[Vinx]

Sorry, forgot one step:

After you pressed F6, a window appears where you can select the process of the application you want to debug (application must be running).

[Mr. Sanders]

Hello Vinx,

thank you for your answer, but we do not have problems to create the scripts or to attach the debugger (see my posting, we already set the breakpoints in the EA debugger).

The problem is, that the breakpoints have white question marks in it it red circle, even if the process is attached.

That means, the breakpoints are not realy attached to the code (see documentation in EA).
This is what we see in the modules tab of the debug workbench.

Only the hosting dll, which load our assembly dynamically are listed in the modules tab, but not the assembly which contains the code.

This worked fine in 7.0.
Now there seem to be problems, with dynamic assemblies.

So we CAN set the break points,
we CAN attach to the process,
but the break points are never reached.

When we start a process explorer, we see that our assembly is loaded.
On the ui we see that the code is running, but the ea is not able to attach the break point to it.

I wrote a bug report in the mean time.

Or is there anybody who can give us a workaround.

Regards
Michael