Bug 39951 - Inconsistent string.EndsWith implementation. Does not recognize null character.
Summary: Inconsistent string.EndsWith implementation. Does not recognize null character.
Status: RESOLVED DUPLICATE of bug 10443
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: master
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Alexander Köplinger [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2016-03-28 17:01 UTC by N. Taylor Mullen
Modified: 2016-04-16 07:59 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED DUPLICATE of bug 10443

Description N. Taylor Mullen 2016-03-28 17:01:11 UTC
I was able to reproduce this issue on Ubuntu 14.04 with mono 4.0.5. Also, this issue may expand to more string methods than EndsWith, it's just the one I encountered.

I ran the following program:
using System;

public class Program
{
    public static void Main(string[] args)
    {
        var val = "something" + '\0';

        Console.WriteLine(val.EndsWith("something"));
    }
}


With Mono this outputs "True". With CoreCLR on Linux and on windows (including net45 on win) this outputs "False".

Seems like an inconsistency in the implementations.
Comment 1 Alexander Köplinger [MSFT] 2016-04-05 01:27:30 UTC
Confirmed with master/a7fb596. I'll take a look, thanks for the report!
Comment 2 Marek Safar 2016-04-16 07:59:57 UTC

*** This bug has been marked as a duplicate of bug 10443 ***