[Mono-bugs] [Bug 542305] Debugging remotely fails when debugging on SLES 11 x86_64 w/Mono-X

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=542305

User martin at novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=542305#c8





--- Comment #8 from Martin Baulig <martin at novell.com>  2009-09-28 09:50:30 MDT ---
Ok, I found the problem - /opt/novell/mono/bin/mono is a shell script, not an
executable.

Unfortunately, we can't support this in the debugger (it'd be really
difficult).  To officially support this we'd need to:

* check whether the current executable is /bin/bash and its command line
arguments point to a shell script
* forcibly override the user's follow-fork configuration to follow fork()s
until we invoked the real mono
* deal with any other child processes the script may invoke somehow
* go back to normal debugging once we got the real mono

I'm afraid this'd not only be a lot of work, but also very error-prone.

To summarize, when starting a shell script, the debugger "thinks" we're
debugging /bin/bash, not mono - so I'd need to follow all fork()s and exec()s
until it's launching the real mono.

Since all the script does is setting LD_LIBRARY_PATH and then invoke the real
mono, we can easily do this in the debugger, we simply need to make sure the
debugger finds the "real" mono executable.

At the moment, we're already setting MONO_GAC_PREFIX, MONO_PATH,
LD_LIBRARY_PATH and PATH to the mono prefix when starting mono inside the
debugger, so we only need to detect the correct mono binary.

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.