svn path=/branches/mono-2-6/mono/; revision=148851
* debugger-agent.c: The end_runtime_invoke guard isn't working on AMD64 as __builtin_frame_address (1) returns NULL. Disable the behaviour by default, and make it runtime configurable. svn path=/branches/mono-2-6/mono/; revision=148421
Simplifies the code a little bit by eliminating the in_quote variable, but also fixes the rules to follow the requirements from the "Shell Command Language" specification on the Unix03 site: http://opengroup.org/onlinepubs/007908775/xcu/chap2.html#tag_001_002 In particular, the interpretation of the backslash inside double quotes is limited to a handful of characters. Notice that this differs from the glib implementation which is not correct either.
…ed quote reset the quoting state This should fix #637680
… ChooseAd The second loop over the ads hashtable must not reject an app if the keyword filter is empty.
Ditto. Fixes bug #636841.
If we are redirecting to a GET from a POST, the Content-Length header might have stale data and it will be sent. Some servers, instead of ignoring it, keep waiting for the data to be sent (for a GET!). Fixes bug #636219.
We were usign teh URL, but that might not be unique among several requests that need to be authenticated using NTLM. This led to different requests sharing the same authentication session which fails miserably. Bug #631315 fixed.
If there's a POST/PUT request that gets a NTLM 401, we save the data and don't send it again until after the challenge phase. Ie, instead of sending all the data 3 times, we only send it at most twice.
Add option to specify toolsversion from the command line, to the man page.
Reported by Lluis Sanchez.
OP_BREAK can take up to 40 bytes on ppc64
The duplicate-element checking algorithm wasn't restricted to just elements; consequently, an 'invalid token' exception was generated from XPath because we were trying to call XmlNode.SelectNodes("#text"), and '#' isn't valid. Oops. Fixes building gendarme from mono-tools.
dist-local: dist-default fixes dist of this dir
This should help with any comparison tools as we ensure that libraries and types are in a consistent order.
Previously, in a (misguided) effort to reduce memory requirements, I loaded the source document into an XDocument, then wrote it piecemeal to an output XmlWriter. - Pro: only one document needed to be kept in memory, and additional memory was only needed to write replacement //Type nodes. - Con: since the output document isn't kept in memory, we can't do any post-processing before writing. Unfortunately, post-processing is what I want to do: I want to order the //Type elements by //Type/@Name, which means I need the entire document in memory _anyway_. Sorting //Type elements is for the next patch; this just migrates to the "do everything in-memory" logic.
Generate the //Type/AssemblyInfo/AssemblyPublicKey and //Type/AssemblyInfo/AssemblyCulture elements based on the values stored in the index.xml file (which is why we updated mdoc-update to store this). If index.xml doesn't contain the //AssemblyCulture element, input a default <AssemblyCulture>neutral</AssemblyCulture> element.
With these changes, we can import the .NET 4.0 reference assembly documentation and validate the output w/o getting any errors. Yes, this means we now accept several elements that aren't part of the ECMA standard, but at least the primary source of information for ECMA will sanely validate...
Screwy docs be screwy, but crashing is worse than importing odd docs.
The //Member/Attributes element would "move" from after //Member/AssemblyInfo to the last element within //Member when updating properties and events. This would result in overly large diff's when no other changes occurred, and results in 'mdoc validate' stating that the file is invalid.
Some source XML documentation uses //returns when it should use //value, so normalize these values on import so we don't get both by mistake.
This way if we import the same documentation file multiple times we won't get duplicate elements into the XML files.
This prevents a file format change for most use cases, and reduces file size diffs when updating assemblies.
…dex.xml. This is so that `mdoc update-ecma-xml` can use this information when generating the /Library/Types/Type elements, as //AssemblyPublicKey and //AssemblyCulture are currently missing from `mdoc update-ecma-xml` output.