Re: [cdt-patch] (ugly) patch: debug configuration fixlet

[Tom Tromey <tromey@xxxxxxxxxx>]

>>>>> "David" == David Inglis <dinglis@xxxxxxx> writes:

David> I take it you are using the gtk SWT? I ask this because I have
David> seen differences wrt listeners between win32 and motif (which I
David> though I fixed) so I suspect there is another difference with
David> gtk.

Yes, apologies for not mentioning that.

David> Until then could you check your .log and make sure there are no
David> exceptions being thrown here, I think something else is
David> happening here other than getConfigForCurrentDebugger()
David> returning null because at the end of the loadDebuggerComboBox
David> is should select the first or previously selected entry there
David> by causing the options page to be created for the debugger.

There aren't any relevant exceptions -- just ones I created by another
mechanism.  (If I click on the debug combo and hit Enter, I get a
StackOverflowError.)

If there's something I can do to help, please let me know.  What I've
observed is that fDCombo.add() will call the notifier (this is before
the setData, hence the null return), but fDCombo.select() doesn't
invoke the notifier.

Perhaps this difference is a bug in the Gtk and/or QNX ports of SWT?
Or perhaps a legitimate difference that requires a workaround like mine?
I don't know enough yet to tell which.

Tom