Hello,
The question here is not about long term but only about 2.0. We want
to support full generic sharing debugging with 2.1, but for 2.0 this
is not an option anymore. So, to recap, from my point of view we have
two sane options for 2.0:
1. Leave generic sharing turned on by default,
Is attaching to a non --debug Mono process a widely used feature?
I do not think this is a good question to ask, because in general
debugging of a Mono program is not even a widely used feature.
A better question to ask is whether developers routinely attach to
running processes to debug with
On Fri, Jul 18, 2008 at 5:27 PM, Miguel de Icaza [EMAIL PROTECTED] wrote:
Is attaching to a non --debug Mono process a widely used feature?
A better question to ask is whether developers routinely attach to
running processes to debug with other debuggers, and I think the answer
to that is
On Tue, 2008-07-15 at 18:05 +0200, Mark Probst wrote:
As I already mentioned on #monodev, my preferred solution for 2.0
would be to disable generic sharing if Mono runs with --debug. In
that case the debugger would work fine without any further changes,
and the users would still benefit from
One word about attaching:
The current situation is that attaching is officially disabled and not
supported (as of July 4th, 2008).
My understanding was that we'll enable generics sharing by default in
Mono 2.0 and I didn't want to tell people that the debugger can do
attaching if that feature
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 would say that we go
On Tue, Jul 15, 2008 at 6:57 PM, Rodrigo Kumpera [EMAIL PROTECTED] 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
On Tue, Jul 15, 2008 at 2:14 PM, Mark Probst [EMAIL PROTECTED] wrote:
On Tue, Jul 15, 2008 at 6:57 PM, Rodrigo Kumpera [EMAIL PROTECTED]
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
On Tue, 2008-07-15 at 19:14 +0200, Mark Probst wrote:
On Tue, Jul 15, 2008 at 6:57 PM, Rodrigo Kumpera [EMAIL PROTECTED] 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
On Tue, Jul 15, 2008 at 7:23 PM, Martin Baulig [EMAIL PROTECTED] wrote:
But keep in mind that we still need to write that check.
That check would be needed in any case, right? Otherwise the debugger
would crash when generic code sharing is turned on, regardless of
whether it's turned on by
10 matches
Mail list logo
