[news.eclipse.tools.cdt] gdb/mi - different behaviour with protocol mi/m

[mwolfram@xxxxxxxx (Mike Wolfram)]

Hi,

I'm running Eclipse 3.4.2 M20090211-1700 with CDT 5.0.2.200902130801 on 
Intel MacOS X 10.5.7. The gdb version is GNU gdb 6.3.50-20050815 (Apple 
version gdb-962) (Sat Jul 26 08:14:40 UTC 2008).

The debug configuration uses gdb/mi as debugger and mi as protocol. The 
command set ist (Standard MAC). If I start debugging all my breakpoints in 
shared libraries are resolved before the initial breakpoint main is 
reached. But I do not have disassembly output. The window shows Pending 
for short moment, then nothing.

Changing the protocol to mi2 results in the opposite behavior. Breakpoints 
in shared libraries aren't activated any more, but I do get the 
disassembly output.

According to gdb docs mi and mi2 should be the same?

I checked with verbose messages on. With protocol mi I see a lot of 
break-insert lines, which I cannot see with protocol mi2. And for the 
disassembly the commands and the response from gdb are obviously the same, 
but in one case they never show up in the disassembly view.

So please tell me what are the differences and how to get it working to 
have breakpoints in shared libs at the same time with disassembly?

Thanx in advance for any help.
--
Mike Wolfram