[Mono-dev] [Ximian-mono-list] Generics Sharing in the Debugger: Request for breaking the code freeze

Rodrigo Kumpera kumpera at gmail.com
Tue Jul 15 13:22:12 EDT 2008

On Tue, Jul 15, 2008 at 2:14 PM, Mark Probst <mark.probst at gmail.com> wrote:

> On Tue, Jul 15, 2008 at 6:57 PM, Rodrigo Kumpera <kumpera at gmail.com>
> wrote:
> > How about disabling generic sharing for the 2.0 release and have a better
> > debugger experience for our users?
> >
> > For me if gsharing breaks the debugger we can't say it's done. Enabling
> by
> > default something that breaks a
> > very important piece of our stack is not the way to go.
> I'm not sure I/we communicated this clearly: If we disable generic
> sharing when --debug is used, which is what we propose, then the only
> scenario that doesn't work is attaching to a Mono process that wasn't
> started with --debug, and the user will get a message saying that to
> attach to such a process it's necessary to start it with -O=-gshared.
> "Normal" debugging (i.e. starting Mono from within the debugger) and
> attaching to a process that was started with --debug will work fine.
> Is attaching to a non --debug Mono process a widely used feature?
> Mark

Ok, seens like a reasonable approach. I don't think attaching is that much
used anyway, so requiring --debug is not an issue, as long as the debugger
a clear error message stating that.

The only downside is that it will make debugging generic sharing bugs a lot
harder, as they
will disappear when running under the debugger. This might confuse the users
a lot.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20080715/23b4bdf0/attachment.html 

More information about the Mono-devel-list mailing list