diff options
author | Marius Ungureanu <teromario@yahoo.com> | 2018-07-25 12:16:17 +0300 |
---|---|---|
committer | Marek Safar <marek.safar@gmail.com> | 2018-07-25 12:16:17 +0300 |
commit | 6b2eafc39db5574bde9e7cf52914c888bb4a2578 (patch) | |
tree | 1c778cfb68581493e8970d892de64ab76d315346 /man | |
parent | d065dc9292e76af34fe2bce3ab2d629acbe1e38c (diff) |
Fix up behaviour of verbose method with arguments (#9087)
* Fix up behaviour of verbose method with arguments
Given a method spec which looks like:
`MainClass:Do(int,int,int)`
Via f024e820a025aacc1cf80eb82a8aee4552c3ac11 the code would match 3 methods:
`MainClass:Do(int`, `int`, `int)`, crashing the runtime.
Accept the multiple method matches via `;`, rather than `,`.
Now, the behaviour is changed so:
`MainClass:Do(int,int,int);MainClass:Do(int,int)`
Get parsed as:
`MainClass:Do(int,int,int)`
`MainClass:Do(int,int)`
* Add tests
* add test file and make tests actually output something
* Smarter unit test around disassembling methods
* Try single quoting environment variable value
* Try using non-throwing setter
Diffstat (limited to 'man')
-rw-r--r-- | man/mono.1 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/man/mono.1 b/man/mono.1 index 8f9f6439f79..7b9ae4eddf9 100644 --- a/man/mono.1 +++ b/man/mono.1 @@ -1897,7 +1897,7 @@ for example, to see managed frame names on gdb backtraces. \fBMONO_VERBOSE_METHOD\fR Enables the maximum JIT verbosity for the specified method. This is very helpfull to diagnose a miscompilation problems of a specific -method. This can be a comma-separated list of method names to +method. This can be a semicolon-separated list of method names to match. If the name is simple, this applies to any method with that name, otherwise you can use a mono method description (see the section METHOD DESCRIPTIONS). |