[Mono-dev] .NET Foundation's Advisory Council
Hey guys, There is still time to join the discussion about the advisory council for the .NET Foundation: http://blogs.msdn.com/b/dotnet/archive/2014/11/24/advisory-council-proposal-call-for-community-feedback-extended-to-december-5th.aspx ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Appveyor builds failing - corlib v112
Hi, Appveyor builds have been failing on get-monolite-latest since commit #33861cf3 I believe this is because mono_corlib_version was changed to 112 and there is no downloadable archive available at http://storage.bos.xamarin.com/mono-dist-master/latest/monolite-112-latest.tar.gz Perhaps I misunderstand, but if I'm correct about this would it be possible for somebody to make that available? Thanks, Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Using .so file in Android Library Project and then using it in an Android App
When I add libcyusb.so, I got this error: "libcyusb.so is not a valid ELF executable" I checked the library, libcyusb.so is not ELF, it is a linker, however libcyusb.so.1 is ELF 64 bit sharerd object. How can add libcyusb.so.1? Because android accepts lib prefix and so suffix. 2014-11-28 12:32 GMT+02:00 Burhan Eyuboglu : > Now, I can add .so file into the csproj. However, a new error occured: > libcyusb.so is not a valid ELF. > > I think while building libcyusb in linux, I should add Android as target > OS. Is that true? If it is, how can I add it to the makefile? Do you know > the commands for it? > > 2014-11-26 19:36 GMT+02:00 Rafael Teixeira : > >> I think you'll need to add it to the application. I'm not sure Android >> will let you install the native lib in any valid place afterwards, like >> extracting it from an embedded resource and writing to a file, but I might >> be wrong... Wait for the experts to chime in... >> >> >> On Wed Nov 26 2014 at 3:05:25 PM Burhan Eyuboglu < >> burhaneyubo...@gmail.com> wrote: >> >>> Is valid for adding .so file to >>> AndroidLibraryProject? I m not trying to add it to AndroidApplication >>> >>> 26 Kasım 2014 Çarşamba tarihinde, Rafael Teixeira >>> yazdı: >>> It should be , that is what Jonathan meant by choosing the action (you can change it on the properties window when selecting the item in the solution explorer), also it is not a good thing to put it inside the Resources folder, it is not an embeddable resource, it will be packed in the apk not in the managed dll. On Wed Nov 26 2014 at 2:08:39 PM Burhan Eyuboglu < burhaneyubo...@gmail.com> wrote: > > > > I have created a lib file in the resources folder, and armeabi-v7a > folder in the lib file and put the libcyusb.so there. When I look at the > csproj file, it has changed like that: > > > Include="Resources\lib\armeabi-v7a\libcyusb.so" /> > > > However, I'm still getting " can not load dll" error: > > [monodroid-debug] Trying to initialize the debugger with options: > --debugger-agent=transport=dt_socket,loglevel=0,address=127.0.0.1:8852 > ,server=y,embedding=1 > [libc] WARNING: generic atexit() called from legacy shared library > [Mono] Image addref mscorlib[0x5ac6bfe0] -> mscorlib.dll[0x5ace0fa0]: 1 > [Mono] AOT module 'mscorlib.dll.so' not found: Cannot load library: > load_library(linker.cpp:746): library > "/data/data/LibraryDenemesi.LibraryDenemesi/lib/mscorlib.dll.so" not > found > [Mono] Assembly mscorlib[0x5ac6bfe0] added to domain RootDomain, > ref_count=1 > [Mono] Assembly Loader probing location: > '/storage/emulated/0/Android/data/LibraryDenemesi.LibraryDenemesi/files/.__override__/LibraryDenemesi.dll'. > [Mono] Image addref LibraryDenemesi[0x5c771638] -> > /storage/emulated/0/Android/data/LibraryDenemesi.LibraryDenemesi/files/.__override__/LibraryDenemesi.dll[0x5bb190f0]: > 2 > [Mono] Assembly LibraryDenemesi[0x5c771638] added to domain > RootDomain, ref_count=1 > [Mono] AOT module > '/storage/emulated/0/Android/data/LibraryDenemesi.LibraryDenemesi/files/.__override__/ > LibraryDenemesi.dll.so' not found: Cannot load library: > load_library(linker.cpp:746): library > "/data/data/LibraryDenemesi.LibraryDenemesi/lib//storage/emulated/0/Android/data/LibraryDenemesi.LibraryDenemesi/files/.__override__/ > LibraryDenemesi.dll.so" not found > [Mono] Assembly Loader loaded assembly from location: > '/storage/emulated/0/Android/data/LibraryDenemesi.LibraryDenemesi/files/.__override__/LibraryDenemesi.dll'. > [Mono] Config attempting to parse: > '/storage/emulated/0/Android/data/LibraryDenemesi.LibraryDenemesi/files/.__override__/LibraryDenemesi.dll.config'. > [Mono] Config attempting to parse: > '/Users/builder/data/lanes/monodroid-mlion-monodroid-4.20-series/ba9bbbdd/source/monodroid/builds/install/mono-armv7/etc/mono/assemblies/LibraryDenemesi/LibraryDenemesi.config'. > [Mono] Image addref CypressLibrary[0x5ac25fb0] -> > CypressLibrary.dll[0x5bb1a420]: 1 > [Mono] Assembly CypressLibrary[0x5ac25fb0] added to domain RootDomain, > ref_count=1 > [Mono] AOT module 'CypressLibrary.dll.so' not found: Cannot load > library: load_library(linker.cpp:746): library > "/data/data/LibraryDenemesi.LibraryDenemesi/lib/CypressLibrary.dll.so" > not found > [monodroid-gc] GREF GC Threshold: 46800 > [Mono] Image addref Mono.Android[0x5aa93670] -> > Mono.Android.dll[0x5ace36c8]: 1 > [Mono] Assembly Mono.Android[0x5aa93670] added to domain RootDomain, > ref_count=1 > [Mono] AOT module 'Mono.Android.dll.so' not found: Cannot load > library: load_library(linker.cpp:746): library > "/data/data/LibraryDenemesi.LibraryDenemesi/lib/Mono.Android.dll.so" > not found > [Mono] Assembly Ref addref Mono.Android[0x5aa93670] -> >
Re: [Mono-dev] How to report bug in mono/monodevelop/nuget?
On 02/12/2014 11:23, Alexander Köplinger wrote: > You can file Mono and MonoDevelop bugs at https://bugzilla.xamarin.com Don't know if it is the best place but... done. :D https://bugzilla.xamarin.com/show_bug.cgi?id=24991 federico -- Federico Di Gregorio federico.digrego...@dndg.it Di Nunzio & Di Gregorio srl http://dndg.it Non vi sono certezze, solo opportunità. -- V ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] file handle leak in cpu_load
I opened a PR on your behalf: https://github.com/mono/mono/pull/1434
-- Alex
> Date: Tue, 2 Dec 2014 13:02:54 +0100
> From: markus.b...@zkrd.de
> To: alex.koeplin...@outlook.com
> CC: mono-devel-list@lists.ximian.com
> Subject: Re: [Mono-dev] file handle leak in cpu_load
>
> Not easily, as I do not have an account on GitHub.
>
> Am Tue, 2 Dec 2014 12:12:04 +0100
> schrieb Alexander Köplinger :
>
> > Can you send a pull request on GitHub?
> >
> > > Date: Tue, 2 Dec 2014 12:01:29 +0100
> > > From: markus.b...@zkrd.de
> > > To: mono-devel-list@lists.ximian.com
> > > Subject: [Mono-dev] file handle leak in cpu_load
> > >
> > > Hi all,
> > >
> > > last week we used the profiler of a mono 3.10.0 installation on
> > > Linux x86_64 and we found it leaks file handles (for /proc/loadavg).
> > >
> > > I located the problem in the function cpu_load in
> > > mono/utils/mono-counters.c. If a premature return is taken, the
> > > FILE pointer f is not fclose()-ed.
> > >
> > > I propose the following fix:
> > >
> > > ---
> > > mono/utils/mono-counters.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/mono/utils/mono-counters.c b/mono/utils/mono-counters.c
> > > index 1e0840c..c669454 100644
> > > --- a/mono/utils/mono-counters.c
> > > +++ b/mono/utils/mono-counters.c
> > > @@ -360,6 +360,7 @@ cpu_load (int kind)
> > > FILE *f = fopen ("/proc/loadavg", "r");
> > > if (f) {
> > > len = fread (buffer, 1, sizeof (buffer) - 1, f);
> > > + fclose (f);
> > > if (len > 0) {
> > > buffer [len < 511 ? len : 511] = 0;
> > > b = buffer;
> > > @@ -374,7 +375,6 @@ cpu_load (int kind)
> > > }
> > > }
> > > }
> > > - fclose (f);
> > > }
> > > #endif
> > > return 0;
> > > --
> > >
> > > It applies on master and also (with an offset of -32 lines) on
> > > mono-3.10.0-branch.
> > >
> > > What do you think?
> > >
> > > Regards,
> > > Markus
> > > ___
> > > Mono-devel-list mailing list
> > > Mono-devel-list@lists.ximian.com
> > > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >
>
>
> --
> Markus Beth ZKRD
> Software DeveloperZentrales Knochenmarkspender-Register
> Fon: +49 731 1507-421 fuer die Bundesrepublik Deutschland
> Fax: +49 731 1507-502 Gemeinnuetzige Gesellschaft mbH
> http://www.zkrd.de/ Helmholtzstraße 10, 89081 Ulm, Germany
> -
> Registergericht: Amtsgericht Ulm, HRB 2566, UID-Nr.: DE269639005
> Geschäftsführer: Dr. Peter Mein und Dr. Dr. Carlheinz Müller
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] file handle leak in cpu_load
Not easily, as I do not have an account on GitHub.
Am Tue, 2 Dec 2014 12:12:04 +0100
schrieb Alexander Köplinger :
> Can you send a pull request on GitHub?
>
> > Date: Tue, 2 Dec 2014 12:01:29 +0100
> > From: markus.b...@zkrd.de
> > To: mono-devel-list@lists.ximian.com
> > Subject: [Mono-dev] file handle leak in cpu_load
> >
> > Hi all,
> >
> > last week we used the profiler of a mono 3.10.0 installation on
> > Linux x86_64 and we found it leaks file handles (for /proc/loadavg).
> >
> > I located the problem in the function cpu_load in
> > mono/utils/mono-counters.c. If a premature return is taken, the
> > FILE pointer f is not fclose()-ed.
> >
> > I propose the following fix:
> >
> > ---
> > mono/utils/mono-counters.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/mono/utils/mono-counters.c b/mono/utils/mono-counters.c
> > index 1e0840c..c669454 100644
> > --- a/mono/utils/mono-counters.c
> > +++ b/mono/utils/mono-counters.c
> > @@ -360,6 +360,7 @@ cpu_load (int kind)
> > FILE *f = fopen ("/proc/loadavg", "r");
> > if (f) {
> > len = fread (buffer, 1, sizeof (buffer) - 1, f);
> > + fclose (f);
> > if (len > 0) {
> > buffer [len < 511 ? len : 511] = 0;
> > b = buffer;
> > @@ -374,7 +375,6 @@ cpu_load (int kind)
> > }
> > }
> > }
> > - fclose (f);
> > }
> > #endif
> > return 0;
> > --
> >
> > It applies on master and also (with an offset of -32 lines) on
> > mono-3.10.0-branch.
> >
> > What do you think?
> >
> > Regards,
> > Markus
> > ___
> > Mono-devel-list mailing list
> > Mono-devel-list@lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
--
Markus Beth ZKRD
Software DeveloperZentrales Knochenmarkspender-Register
Fon: +49 731 1507-421 fuer die Bundesrepublik Deutschland
Fax: +49 731 1507-502 Gemeinnuetzige Gesellschaft mbH
http://www.zkrd.de/ Helmholtzstraße 10, 89081 Ulm, Germany
-
Registergericht: Amtsgericht Ulm, HRB 2566, UID-Nr.: DE269639005
Geschäftsführer: Dr. Peter Mein und Dr. Dr. Carlheinz Müller
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono for Windows test build (Mono-devel-list Digest, Vol 116, Issue 2)
> > Btw. build.bat could be integrated into the bash files quite easily > > I think (for consistency), it just invokes msbuild. > > It already is, in the top-level scripts What I meant was getting rid of build.bat completely and just invoking MSBuild directly like you do here: https://github.com/directhex/newbuilder/blob/455c8d58774bfb6ecf1dff847c47f4c6eeabec47/defs/mono#L60 -- Alex ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono for Windows test build (Mono-devel-list Digest, Vol 116, Issue 2)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/12/14 19:41, Alexander K?plinger wrote: > Hey Jo, I tried it and it installed fine for me. However, the > version is currently set to 3.12.1 in > https://github.com/directhex/newbuilder/blob/master/resources/build.bat > and > https://github.com/directhex/newbuilder/blob/master/resources/bat/setmonopath.bat, > I guess we should change that to 3.12.0. Yeah, that's an oops. I fixed it and didn't commit it and reset the branch and blah blah blah. > Btw. build.bat could be integrated into the bash files quite easily > I think (for consistency), it just invokes msbuild. It already is, in the top-level scripts > The BCL assemblies are taken from the 3.10 MDK installer as far as > I can see? The BCL is cygwin-built from the same revision as the runtime. F#, IPy, IR and Boo are copied from the last green internal MDK 3.12 branch build. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUfaIyAAoJEMkPnLkOH60M/rAH/3A+jjDGYzWT09tmPbTr1k6A sl6tReEQH3vfJP6gKcM+7mxtf9zWhd/o6/szwSeI/WJRESI11VQG5sDGspGJURHp N4ZMBF0zOl1MP5kNeUDw/EtuciEQpRTltTv7+RZtxYXFjKXP1rqrV9eZ11SKVdG0 yI/SO/guTycUUcMkWmjhECzYGeUgTeRKiFmk69z5/blb3ZqabBva/xQJ3aw4ra3V wt6GGjuVoNypNF76/Qoo2TfOKZabqKCfkbRgcVJnNdi+1ycENUyDhtER6TNzQH8K 2mGu5A5Deni2PTjWKaYdHlXp57AR7HWnPAmj5B7BovRWhNKcd7+K53Qt00q9+Mw= =gtXE -END PGP SIGNATURE- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] file handle leak in cpu_load
Can you send a pull request on GitHub?
> Date: Tue, 2 Dec 2014 12:01:29 +0100
> From: markus.b...@zkrd.de
> To: mono-devel-list@lists.ximian.com
> Subject: [Mono-dev] file handle leak in cpu_load
>
> Hi all,
>
> last week we used the profiler of a mono 3.10.0 installation on
> Linux x86_64 and we found it leaks file handles (for /proc/loadavg).
>
> I located the problem in the function cpu_load in
> mono/utils/mono-counters.c. If a premature return is taken, the FILE
> pointer f is not fclose()-ed.
>
> I propose the following fix:
>
> ---
> mono/utils/mono-counters.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mono/utils/mono-counters.c b/mono/utils/mono-counters.c
> index 1e0840c..c669454 100644
> --- a/mono/utils/mono-counters.c
> +++ b/mono/utils/mono-counters.c
> @@ -360,6 +360,7 @@ cpu_load (int kind)
> FILE *f = fopen ("/proc/loadavg", "r");
> if (f) {
> len = fread (buffer, 1, sizeof (buffer) - 1, f);
> + fclose (f);
> if (len > 0) {
> buffer [len < 511 ? len : 511] = 0;
> b = buffer;
> @@ -374,7 +375,6 @@ cpu_load (int kind)
> }
> }
> }
> - fclose (f);
> }
> #endif
> return 0;
> --
>
> It applies on master and also (with an offset of -32 lines) on
> mono-3.10.0-branch.
>
> What do you think?
>
> Regards,
> Markus
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] file handle leak in cpu_load
Hi all,
last week we used the profiler of a mono 3.10.0 installation on
Linux x86_64 and we found it leaks file handles (for /proc/loadavg).
I located the problem in the function cpu_load in
mono/utils/mono-counters.c. If a premature return is taken, the FILE
pointer f is not fclose()-ed.
I propose the following fix:
---
mono/utils/mono-counters.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mono/utils/mono-counters.c b/mono/utils/mono-counters.c
index 1e0840c..c669454 100644
--- a/mono/utils/mono-counters.c
+++ b/mono/utils/mono-counters.c
@@ -360,6 +360,7 @@ cpu_load (int kind)
FILE *f = fopen ("/proc/loadavg", "r");
if (f) {
len = fread (buffer, 1, sizeof (buffer) - 1, f);
+ fclose (f);
if (len > 0) {
buffer [len < 511 ? len : 511] = 0;
b = buffer;
@@ -374,7 +375,6 @@ cpu_load (int kind)
}
}
}
- fclose (f);
}
#endif
return 0;
--
It applies on master and also (with an offset of -32 lines) on
mono-3.10.0-branch.
What do you think?
Regards,
Markus
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] How to report bug in mono/monodevelop/nuget?
You can file Mono and MonoDevelop bugs at https://bugzilla.xamarin.com -- Alex > Date: Tue, 2 Dec 2014 10:42:23 +0100 > From: f...@dndg.it > To: mono-devel-list@lists.ximian.com > Subject: [Mono-dev] How to report bug in mono/monodevelop/nuget? > > Hi, > > I think I found a little bug in NuGet when running the package manager > from inside MonoDevelop, but I don't know where to report it. It is > obviously a problem related to how authors name files inside packages > but I have a feeling that it should resolved in the NuGet implementation > as used in MonoDevelop. So, I'll just report it here and hope someone > will redirect me to the correct place. :) > > With NuGet you can specify that your package needs to add some tags > (usually configuration items) to an XML file. You can name it Web.config > or web.config and under Windows (case insensitive file system) > everything goes inside the correct, already existing file. But under > Linux if two package authors use different casing you end up with two > (or more) files each one containing part of the configuration. I know > about MONO_IOMAP but it doesn't seem the right answer in this case. > > Any idea? > > federico > > -- > Federico Di Gregorio federico.digrego...@dndg.it > Di Nunzio & Di Gregorio srl http://dndg.it > A desobediência é uma virtude necessária à criatividade. -- Raul Seixas > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] How to report bug in mono/monodevelop/nuget?
Hi, NuGet home appears to be at: https://nuget.codeplex.com/ They have Issue Tracking there. --- Adar Wesley On Tue, Dec 2, 2014 at 11:42 AM, Federico Di Gregorio wrote: > Hi, > > I think I found a little bug in NuGet when running the package manager > from inside MonoDevelop, but I don't know where to report it. It is > obviously a problem related to how authors name files inside packages > but I have a feeling that it should resolved in the NuGet implementation > as used in MonoDevelop. So, I'll just report it here and hope someone > will redirect me to the correct place. :) > > With NuGet you can specify that your package needs to add some tags > (usually configuration items) to an XML file. You can name it Web.config > or web.config and under Windows (case insensitive file system) > everything goes inside the correct, already existing file. But under > Linux if two package authors use different casing you end up with two > (or more) files each one containing part of the configuration. I know > about MONO_IOMAP but it doesn't seem the right answer in this case. > > Any idea? > > federico > > -- > Federico Di Gregorio federico.digrego...@dndg.it > Di Nunzio & Di Gregorio srl http://dndg.it > A desobediência é uma virtude necessária à criatividade. -- Raul Seixas > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] How to report bug in mono/monodevelop/nuget?
Hi, I think I found a little bug in NuGet when running the package manager from inside MonoDevelop, but I don't know where to report it. It is obviously a problem related to how authors name files inside packages but I have a feeling that it should resolved in the NuGet implementation as used in MonoDevelop. So, I'll just report it here and hope someone will redirect me to the correct place. :) With NuGet you can specify that your package needs to add some tags (usually configuration items) to an XML file. You can name it Web.config or web.config and under Windows (case insensitive file system) everything goes inside the correct, already existing file. But under Linux if two package authors use different casing you end up with two (or more) files each one containing part of the configuration. I know about MONO_IOMAP but it doesn't seem the right answer in this case. Any idea? federico -- Federico Di Gregorio federico.digrego...@dndg.it Di Nunzio & Di Gregorio srl http://dndg.it A desobediência é uma virtude necessária à criatividade. -- Raul Seixas ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
