clibinutils-devel — Discussions on development issues of the project

[Clibinutils-devel] New improved Mono.Cecil coming

[Andrea C. O. <and...@gm...>]

Hi,

there will be a new version of Mono.Cecil
http://evain.net/blog/articles/2010/04/12/mono-cecil-0-9-cecil-light

with few improvements: memory consumption, debug support, ...
but ... its API is not backward compatible.
We will see how much it changed and how easy is to support the new one :)

Andrea

Re: [Clibinutils-devel] Support for MDB debug info to ld

[Andrea C. O. <and...@gm...>]

I changed cil32-objdump to print comments with the line numbers.
This change kind of breaks cil32-objdump,
the original idea was that after objdump, you could do some change in
the text file and afterwards reassemble it.
What I originally wanted was to be able to dump and reassemble it
without loosing info.
Now it looses the line numbers; my current change dumps just comments.

I looked only at the instruction code stream, there may be some
problem with position info attached to members (fields or methods) in
Cecil.

BTW In http://groups.google.it/group/mono-cecil?hl=it someone have
problems with debug info.
I do not know how mature is in Cecil the debug info handling.

Andrea

On Tue, Apr 6, 2010 at 2:30 PM, Thierry Lafage <thi...@in...> wrote:
> Hi Andrea,
>
> Even with the Cecil patch, it seems it does not work...
> I recompiled my test program (named induction.dbg.exe) and try to debug it
> with mdb. The link still generates an .mdb file which is (a bit) smaller
> than the original .o.mdb... What I found strange is that when I ask mdb to
> list the source main method, it displays a main method which is not the main
> method of my test program! Also, I set up a breakpoint at main, but mdb
> never stops in the main of the program being debugged...
> You'll find below some output.
> How did you check that your ld merges well all input .mdb files?
>
> Regards,
>
> Thierry Lafage.
>
>
> lafage$ ls -l
> induction.dbg.*
> -rwxr-x--- 1 lafage alf 3072 2010-04-06 14:11
> induction.dbg.exe*
> -rw-r----- 1 lafage alf  405 2010-04-06 14:11
> induction.dbg.exe.mdb
> -rw-r----- 1 lafage alf 3584 2010-04-01 11:37
> induction.dbg.o
> -rw-r----- 1 lafage alf  485 2010-04-01 11:37
> induction.dbg.o.mdb
> -rwxr-x--- 1 lafage alf 4392 2010-04-01 11:37
> induction.dbg.s*
> -rw-r----- 1 lafage alf  112 2010-04-01 11:24
> induction.dbg.s.mdb
> lafage@dingdong src$ cil32-mdb induction.dbg.exe
> Mono Debugger
> (mdb) b main
> Breakpoint 3 at main
> (mdb) l main
> ERROR: No target.
> (mdb) run
> Starting program: induction.dbg.exe
> Cannot read symbol file `/udd/lafage/gcc/image/lib/gcc4net.dll.mdb': Could
> not find file "/udd/lafage/gcc/image/lib/gcc4net.dll.mdb".
> Cannot read symbol file `/udd/lafage/gcc/image/lib/libstd.dll.mdb': Could
> not find file "/udd/lafage/gcc/image/lib/libstd.dll.mdb".
> Thread @1 stopped at #0: 0xb67c720d in <induction.dbg:.start
> (string[])>+0x15 at 1.
>    1 IL_0000: call      0x06000001
> (mdb) l main
>    1 #include <config.h>
>    2 #include "mini.h"
>    3 #ifndef PLATFORM_WIN32
>    4 #include "buildver.h"
>    5 #endif
>    6
>    7 #ifdef PLATFORM_WIN32
>    8
>    9 int
>   10 main ()
>   11 {
>   12    int argc;
>   13    gunichar2** argvw;
>   14    gchar** argv;
>   15    int i;
>   16
>   17    argvw = CommandLineToArgvW (GetCommandLine (), &argc);
>   18    argv = g_new0 (gchar*, argc + 1);
>   19    for (i = 0; i < argc; i++)
>   20            argv [i] = g_utf16_to_utf8 (argvw [i], -1, NULL, NULL,
> NULL);
> (mdb) c
> Cannot read symbol file
> `/udd/lafage/gcc/image/lib/MSCorelibWrapper.dll.mdb': Could not find file
> "/udd/lafage/gcc/image/lib/MSCorelibWrapper.dll.mdb".
> <HERE IS THE OUTPUT OF MY TEST PROGRAM>
> Thread @1 exited.
> Process #1 exited.
> (mdb) Target exited.
>
> Thierry Lafage a écrit :
>
> Andrea,
>
> I did not see your patch for Cecil inthe bugzilla... So, I'll try it
> Sorry,
>
> Thierry Lafage.
>
>
>
> Thierry Lafage a écrit :
>
>
> Hi Andrea,
>
> Thanks for fixing it. By the way, I can't have it working properly.
> I generate a .s with line numbers. Then I use my patched ilasm to
> generated a .o and a .o.mdb.
> Then I use your new ld to make a .exe and a .exe.mdb
> It actually produces a .exe.mdb, but it seems that it does not contain
> the correct information: I run mdb on the .exe and "list main" does not
> list the main of the program but something else I don't understand...
> Moreover, the .exe.mdb is smaller than the .o.mdb ; I think the .exe.mdb
> may be at least as big as the .o.mdb since it should include it,
> shouldn't it?
>
> $ ls -l
> -rw-r----- 1 lafage alf  671 2010-03-31 14:21 induction.c
> -rwxr-x--- 1 lafage alf 3072 2010-04-01 11:56 induction.exe*
> -rw-r----- 1 lafage alf  112 2010-04-01 11:56 induction.exe.mdb
> -rw-r----- 1 lafage alf 3584 2010-04-01 11:37 induction.o
> -rw-r----- 1 lafage alf  485 2010-04-01 11:37 induction.o.mdb
> -rwxr-x--- 1 lafage alf 4392 2010-04-01 11:37 induction.s*
> -rw-r----- 1 lafage alf 3648 2010-03-31 14:22 induction.s
>
> Any clue?
>
> Thierry Lafage.
>
>
>
> Andrea Carlo Ornstein a écrit :
>
>
>
> There is a bug in Mono.Cecil
> https://bugzilla.novell.com/show_bug.cgi?id=592849
>
> otherwise it seems to be working.
> At least small examples.
> I looked ONLY at line numbers in the code stream.
> We do not do anything special for the debug information.
> If there is a problem it would be from mono. Cecil :)
>
> I added the option -g to cil32-as
> it has to be passed down when -g is passed to gcc.
>
> I use this change:
> Index: gcc/config/cil32/cil32.h
> ===================================================================
> --- gcc/config/cil32/cil32.h    (revision 157653)
> +++ gcc/config/cil32/cil32.h    (working copy)
> @@ -53,7 +53,7 @@
>  #else
>  #error "Unrecognized binutils: impossible to choose default compiler
> driver arguments"
>  #endif
> -#define ASM_SPEC "%{!O0:%{O*:-O}}"
> +#define ASM_SPEC "%{!O0:%{O*:-O}} %{g*:-g}"
>  #define LIB_SPEC "-l libstd.dll"
>  #define LINK_SPEC "%{shared:--shared} %{mthreads:-mt}"
>  #define STARTFILE_SPEC ""
>
>
> Andrea
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Clibinutils-devel mailing list
> Cli...@li...
> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>

Re: [Clibinutils-devel] Support for MDB debug info to ld

[Thierry L. <thi...@in...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Andrea,<br>
<br>
Even with the Cecil patch, it seems it does not work...<br>
I recompiled my test program (named induction.dbg.exe) and try to debug
it with mdb. The link still generates an .mdb file which is (a bit)
smaller than the original .o.mdb... What I found strange is that when I
ask mdb to list the source main method, it displays a main method which
is not the main method of my test program! Also, I set up a breakpoint
at main, but mdb never stops in the main of the program being
debugged...<br>
You'll find below some output.<br>
How did you check that your ld merges well all input .mdb files?<br>
<br>
Regards,<br>
<pre class="moz-signature" cols="72">Thierry Lafage.
</pre>
<br>
<br>
<blockquote><tt>lafage$ ls -l
induction.dbg.*                                                                              
  <br>
-rwxr-x--- 1 lafage alf 3072 2010-04-06 14:11
induction.dbg.exe*                                                     
  <br>
-rw-r----- 1 lafage alf  405 2010-04-06 14:11
induction.dbg.exe.mdb                                                  
  <br>
-rw-r----- 1 lafage alf 3584 2010-04-01 11:37
induction.dbg.o                                                        
  <br>
-rw-r----- 1 lafage alf  485 2010-04-01 11:37
induction.dbg.o.mdb                                                    
  <br>
-rwxr-x--- 1 lafage alf 4392 2010-04-01 11:37
induction.dbg.s*                                                       
  <br>
-rw-r----- 1 lafage alf  112 2010-04-01 11:24
induction.dbg.s.mdb                                                    
  <br>
lafage@dingdong src$ cil32-mdb induction.dbg.exe<br>
Mono Debugger                                   <br>
(mdb) b main                                    <br>
Breakpoint 3 at main                            <br>
(mdb) l main                                    <br>
ERROR: No target.<br>
(mdb) run<br>
Starting program: induction.dbg.exe<br>
Cannot read symbol file `/udd/lafage/gcc/image/lib/gcc4net.dll.mdb':
Could not find file "/udd/lafage/gcc/image/lib/gcc4net.dll.mdb".<br>
Cannot read symbol file `/udd/lafage/gcc/image/lib/libstd.dll.mdb':
Could not find file "/udd/lafage/gcc/image/lib/libstd.dll.mdb".<br>
Thread @1 stopped at #0: 0xb67c720d in &lt;induction.dbg:.start
(string[])&gt;+0x15 at 1.<br>
   1 IL_0000: call      0x06000001<br>
(mdb) l main<br>
   1 #include &lt;config.h&gt;<br>
   2 #include "mini.h"<br>
   3 #ifndef PLATFORM_WIN32<br>
   4 #include "buildver.h"<br>
   5 #endif<br>
   6<br>
   7 #ifdef PLATFORM_WIN32<br>
   8<br>
   9 int<br>
  10 main ()<br>
  11 {<br>
  12    int argc;<br>
  13    gunichar2** argvw;<br>
  14    gchar** argv;<br>
  15    int i;<br>
  16<br>
  17    argvw = CommandLineToArgvW (GetCommandLine (), &amp;argc);<br>
  18    argv = g_new0 (gchar*, argc + 1);<br>
  19    for (i = 0; i &lt; argc; i++)<br>
  20            argv [i] = g_utf16_to_utf8 (argvw [i], -1, NULL, NULL,
NULL);<br>
(mdb) c<br>
Cannot read symbol file
`/udd/lafage/gcc/image/lib/MSCorelibWrapper.dll.mdb': Could not find
file "/udd/lafage/gcc/image/lib/MSCorelibWrapper.dll.mdb".<br>
&lt;HERE IS THE OUTPUT OF MY TEST PROGRAM&gt;<br>
Thread @1 exited.<br>
Process #1 exited.<br>
(mdb) Target exited.<br>
  </tt></blockquote>
<br>
Thierry Lafage a écrit :
<blockquote cite="mid:4BB...@in..." type="cite">
  <pre wrap="">Andrea,

I did not see your patch for Cecil inthe bugzilla... So, I'll try it
Sorry,

Thierry Lafage.



Thierry Lafage a écrit :
  </pre>
  <blockquote type="cite">
    <pre wrap="">Hi Andrea,

Thanks for fixing it. By the way, I can't have it working properly.
I generate a .s with line numbers. Then I use my patched ilasm to 
generated a .o and a .o.mdb.
Then I use your new ld to make a .exe and a .exe.mdb
It actually produces a .exe.mdb, but it seems that it does not contain 
the correct information: I run mdb on the .exe and "list main" does not 
list the main of the program but something else I don't understand...
Moreover, the .exe.mdb is smaller than the .o.mdb ; I think the .exe.mdb 
may be at least as big as the .o.mdb since it should include it, 
shouldn't it?

$ ls -l
-rw-r----- 1 lafage alf  671 2010-03-31 14:21 induction.c
-rwxr-x--- 1 lafage alf 3072 2010-04-01 11:56 induction.exe*
-rw-r----- 1 lafage alf  112 2010-04-01 11:56 induction.exe.mdb
-rw-r----- 1 lafage alf 3584 2010-04-01 11:37 induction.o
-rw-r----- 1 lafage alf  485 2010-04-01 11:37 induction.o.mdb
-rwxr-x--- 1 lafage alf 4392 2010-04-01 11:37 induction.s*
-rw-r----- 1 lafage alf 3648 2010-03-31 14:22 induction.s

Any clue?

Thierry Lafage.



Andrea Carlo Ornstein a écrit :
  
    </pre>
    <blockquote type="cite">
      <pre wrap="">There is a bug in Mono.Cecil
<a class="moz-txt-link-freetext" href="https://bugzilla.novell.com/show_bug.cgi?id=592849">https://bugzilla.novell.com/show_bug.cgi?id=592849</a>

otherwise it seems to be working.
At least small examples.
I looked ONLY at line numbers in the code stream.
We do not do anything special for the debug information.
If there is a problem it would be from mono. Cecil :)

I added the option -g to cil32-as
it has to be passed down when -g is passed to gcc.

I use this change:
Index: gcc/config/cil32/cil32.h
===================================================================
--- gcc/config/cil32/cil32.h    (revision 157653)
+++ gcc/config/cil32/cil32.h    (working copy)
@@ -53,7 +53,7 @@
 #else
 #error "Unrecognized binutils: impossible to choose default compiler
driver arguments"
 #endif
-#define ASM_SPEC "%{!O0:%{O*:-O}}"
+#define ASM_SPEC "%{!O0:%{O*:-O}} %{g*:-g}"
 #define LIB_SPEC "-l libstd.dll"
 #define LINK_SPEC "%{shared:--shared} %{mthreads:-mt}"
 #define STARTFILE_SPEC ""


Andrea



    
      </pre>
    </blockquote>
  </blockquote>
  <pre wrap=""><!---->
------------------------------------------------------------------------------
Download Intel&amp;#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/intel-sw-dev">http://p.sf.net/sfu/intel-sw-dev</a>
_______________________________________________
Clibinutils-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Cli...@li...">Cli...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/clibinutils-devel">https://lists.sourceforge.net/lists/listinfo/clibinutils-devel</a>
  </pre>
</blockquote>
</body>
</html>

Re: [Clibinutils-devel] Support for MDB debug info to ld

[Thierry L. <thi...@in...>]

Andrea,

I did not see your patch for Cecil inthe bugzilla... So, I'll try it
Sorry,

Thierry Lafage.



Thierry Lafage a écrit :
> Hi Andrea,
>
> Thanks for fixing it. By the way, I can't have it working properly.
> I generate a .s with line numbers. Then I use my patched ilasm to 
> generated a .o and a .o.mdb.
> Then I use your new ld to make a .exe and a .exe.mdb
> It actually produces a .exe.mdb, but it seems that it does not contain 
> the correct information: I run mdb on the .exe and "list main" does not 
> list the main of the program but something else I don't understand...
> Moreover, the .exe.mdb is smaller than the .o.mdb ; I think the .exe.mdb 
> may be at least as big as the .o.mdb since it should include it, 
> shouldn't it?
>
> $ ls -l
> -rw-r----- 1 lafage alf  671 2010-03-31 14:21 induction.c
> -rwxr-x--- 1 lafage alf 3072 2010-04-01 11:56 induction.exe*
> -rw-r----- 1 lafage alf  112 2010-04-01 11:56 induction.exe.mdb
> -rw-r----- 1 lafage alf 3584 2010-04-01 11:37 induction.o
> -rw-r----- 1 lafage alf  485 2010-04-01 11:37 induction.o.mdb
> -rwxr-x--- 1 lafage alf 4392 2010-04-01 11:37 induction.s*
> -rw-r----- 1 lafage alf 3648 2010-03-31 14:22 induction.s
>
> Any clue?
>
> Thierry Lafage.
>
>
>
> Andrea Carlo Ornstein a écrit :
>   
>> There is a bug in Mono.Cecil
>> https://bugzilla.novell.com/show_bug.cgi?id=592849
>>
>> otherwise it seems to be working.
>> At least small examples.
>> I looked ONLY at line numbers in the code stream.
>> We do not do anything special for the debug information.
>> If there is a problem it would be from mono. Cecil :)
>>
>> I added the option -g to cil32-as
>> it has to be passed down when -g is passed to gcc.
>>
>> I use this change:
>> Index: gcc/config/cil32/cil32.h
>> ===================================================================
>> --- gcc/config/cil32/cil32.h    (revision 157653)
>> +++ gcc/config/cil32/cil32.h    (working copy)
>> @@ -53,7 +53,7 @@
>>  #else
>>  #error "Unrecognized binutils: impossible to choose default compiler
>> driver arguments"
>>  #endif
>> -#define ASM_SPEC "%{!O0:%{O*:-O}}"
>> +#define ASM_SPEC "%{!O0:%{O*:-O}} %{g*:-g}"
>>  #define LIB_SPEC "-l libstd.dll"
>>  #define LINK_SPEC "%{shared:--shared} %{mthreads:-mt}"
>>  #define STARTFILE_SPEC ""
>>
>>
>> Andrea
>>
>>
>>
>>     

Re: [Clibinutils-devel] Support for MDB debug info to ld

[Thierry L. <thi...@in...>]

Hi Andrea,

Thanks for fixing it. By the way, I can't have it working properly.
I generate a .s with line numbers. Then I use my patched ilasm to 
generated a .o and a .o.mdb.
Then I use your new ld to make a .exe and a .exe.mdb
It actually produces a .exe.mdb, but it seems that it does not contain 
the correct information: I run mdb on the .exe and "list main" does not 
list the main of the program but something else I don't understand...
Moreover, the .exe.mdb is smaller than the .o.mdb ; I think the .exe.mdb 
may be at least as big as the .o.mdb since it should include it, 
shouldn't it?

$ ls -l
-rw-r----- 1 lafage alf  671 2010-03-31 14:21 induction.c
-rwxr-x--- 1 lafage alf 3072 2010-04-01 11:56 induction.exe*
-rw-r----- 1 lafage alf  112 2010-04-01 11:56 induction.exe.mdb
-rw-r----- 1 lafage alf 3584 2010-04-01 11:37 induction.o
-rw-r----- 1 lafage alf  485 2010-04-01 11:37 induction.o.mdb
-rwxr-x--- 1 lafage alf 4392 2010-04-01 11:37 induction.s*
-rw-r----- 1 lafage alf 3648 2010-03-31 14:22 induction.s

Any clue?

Thierry Lafage.



Andrea Carlo Ornstein a écrit :
> There is a bug in Mono.Cecil
> https://bugzilla.novell.com/show_bug.cgi?id=592849
>
> otherwise it seems to be working.
> At least small examples.
> I looked ONLY at line numbers in the code stream.
> We do not do anything special for the debug information.
> If there is a problem it would be from mono. Cecil :)
>
> I added the option -g to cil32-as
> it has to be passed down when -g is passed to gcc.
>
> I use this change:
> Index: gcc/config/cil32/cil32.h
> ===================================================================
> --- gcc/config/cil32/cil32.h    (revision 157653)
> +++ gcc/config/cil32/cil32.h    (working copy)
> @@ -53,7 +53,7 @@
>  #else
>  #error "Unrecognized binutils: impossible to choose default compiler
> driver arguments"
>  #endif
> -#define ASM_SPEC "%{!O0:%{O*:-O}}"
> +#define ASM_SPEC "%{!O0:%{O*:-O}} %{g*:-g}"
>  #define LIB_SPEC "-l libstd.dll"
>  #define LINK_SPEC "%{shared:--shared} %{mthreads:-mt}"
>  #define STARTFILE_SPEC ""
>
>
> Andrea
>
>
> On Wed, Mar 31, 2010 at 4:05 PM, Andrea Carlo Ornstein
> <and...@gm...> wrote:
>   
>> I am sorry,
>> I added the build of the library, not the use of it. :)
>> That part is not done yet.
>> For it I have to look in my old directories.
>> But I guess it would be just a small change in
>> CFileFactory.cs:LoadCFile() and CFile.cs:Save()
>>
>> There is a svn property 'svn:extrenals' that properly configured does
>> the co of remotes svn dirs.
>> I never properly checked the license from Mono for this kind of use of
>> the libraries;
>> and the fact that we co them and build them the way we do is really a hack.
>> We should just pick the ones installed by mono on the machine.
>> That's way the property is not set on trunk.
>>
>> But since it is really convenient I use it in my development branch :)
>>
>> Andrea
>>
>> On Wed, Mar 31, 2010 at 3:11 PM, Thierry Lafage <thi...@in...> wrote:
>>     
>>> Hi Andrea,
>>>
>>> Great job!
>>> However, I don't see how to use it... I mean how does ld merge together
>>> all *.mdb files into an eg. a.out.mdb?
>>> Is there any new option to use?
>>> I tried on a simple example, and it didn't produce any mdb file...
>>>
>>> By the way, when I checkouted your branch, it automatically checkouted
>>> Cecil, Cecil.Mdb and CompilerServices.SymbolWriter. It looks... magic!
>>> If you can do the same for the trunk, the upgrade shouldn't be a pb.,
>>> should it?
>>>
>>> Regards,
>>>
>>> Thierry Lafage.
>>>
>>>
>>>
>>> Andrea Carlo Ornstein a écrit :
>>>       
>>>> Hi,
>>>>
>>>> I ci the changes in my dev branch
>>>> (https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/branches/aco-dev),
>>>> it seems to be working fine.
>>>>
>>>> If I do the ci on trunk all the people that builds the binutils have
>>>> to co two extra dirs from Mono.
>>>> It will break all current checkouts.
>>>>
>>>> Let me know when you want me to ci on trunk.
>>>>
>>>> Andrea
>>>>
>>>>
>>>> On Mon, Mar 29, 2010 at 4:26 PM, Andrea Carlo Ornstein
>>>> <and...@gm...> wrote:
>>>>
>>>>         
>>>>> I am not in the office at the moment, I need a couple of days to see
>>>>> what I have.
>>>>> Perhaps it's already done :)
>>>>> I just do not remember.
>>>>>
>>>>> I worked on it more than a year ago when I was writing the binutils.
>>>>>
>>>>> Andrea
>>>>>
>>>>> On Mon, Mar 29, 2010 at 3:45 PM, Thierry Lafage <thi...@in...> wrote:
>>>>>
>>>>>           
>>>>>> Hi Andrea,
>>>>>>
>>>>>> I think that 2 more checkout points is not a problem provided that it is
>>>>>> correctly documented and because there is already the dependency wrt. Cecil.
>>>>>> The real problem is, I guess, how much work would it be to add this support
>>>>>> and what has to be done.
>>>>>> Then, given that it is not our top priority either, who should (or would be
>>>>>> willing to) do the work?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Thierry Lafage.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Andrea Carlo Ornstein a écrit :
>>>>>>
>>>>>>             
>>>>>>> Hi,
>>>>>>>
>>>>>>> I actually tried to solve the problem a while ago,
>>>>>>> after a while I give up. :)
>>>>>>> It was not a priority at the time, we just would have two extra checkout
>>>>>>> points.
>>>>>>>
>>>>>>> The right solution would be to use the libraries installed in the
>>>>>>> machine you are building on (the same apply to Mono.Cecil).
>>>>>>>
>>>>>>> For Cecil this was always a problem, on my machine, a Debian (but also
>>>>>>> on ubuntu) the library they ship is too old.
>>>>>>> That is the reason we check out it from Mono repository and build it
>>>>>>> from scratch.
>>>>>>>
>>>>>>> We can use the one installed in the machine if they are up to date
>>>>>>> (small change in the e configure.ac)I can provide a patch for it.
>>>>>>> OR
>>>>>>> add two new checkout points and change the Makefile as I did for Cecil
>>>>>>> (Imay still have may changes somewhere in my machine at the office.
>>>>>>>
>>>>>>> Andrea
>>>>>>>
>>>>>>> On Fri, Mar 26, 2010 at 6:10 PM, Thierry Lafage <thi...@in...>
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Some time ago, I added .line information generation in gcc4cli so as to
>>>>>>>> relate cli code to C source code. I'm preparing an ilasm patch to take
>>>>>>>> these .line statements into account and write source information in the
>>>>>>>> corresponding .mdb file.
>>>>>>>> Now, the last stage would be to make ld gather all .mdb files together
>>>>>>>> (with adequate relocation info) to build the a.out.mdb (or .dll.mdb, or
>>>>>>>> ...).
>>>>>>>> I've began to look at Cecil code, and I've found that there is support
>>>>>>>> for mdb files in Mono.Cecil.Mdb (which have to be separately check-outed
>>>>>>>> and have to include Mono.CompilerServices.SymbolWriter, also separately
>>>>>>>> check-outed). But, I really don't know how to do that and whether it
>>>>>>>> would be a lot of work (it seems so to me).
>>>>>>>>
>>>>>>>> People in this list surely have already though of this matter: what is
>>>>>>>> your opinion? Would there be someone willing to develop it (maybe I
>>>>>>>> would if it's not a lot of work)?
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Thierry Lafage.
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Download Intel&#174; Parallel Studio Eval
>>>>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>>>> _______________________________________________
>>>>>>>> Clibinutils-devel mailing list
>>>>>>>> Cli...@li...
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>> ------------------------------------------------------------------------------
>>> Download Intel&#174; Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Clibinutils-devel mailing list
>>> Cli...@li...
>>> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>>>
>>>       

Re: [Clibinutils-devel] Support for MDB debug info to ld

[Andrea C. O. <and...@gm...>]

There is a bug in Mono.Cecil
https://bugzilla.novell.com/show_bug.cgi?id=592849

otherwise it seems to be working.
At least small examples.
I looked ONLY at line numbers in the code stream.
We do not do anything special for the debug information.
If there is a problem it would be from mono. Cecil :)

I added the option -g to cil32-as
it has to be passed down when -g is passed to gcc.

I use this change:
Index: gcc/config/cil32/cil32.h
===================================================================
--- gcc/config/cil32/cil32.h    (revision 157653)
+++ gcc/config/cil32/cil32.h    (working copy)
@@ -53,7 +53,7 @@
 #else
 #error "Unrecognized binutils: impossible to choose default compiler
driver arguments"
 #endif
-#define ASM_SPEC "%{!O0:%{O*:-O}}"
+#define ASM_SPEC "%{!O0:%{O*:-O}} %{g*:-g}"
 #define LIB_SPEC "-l libstd.dll"
 #define LINK_SPEC "%{shared:--shared} %{mthreads:-mt}"
 #define STARTFILE_SPEC ""


Andrea


On Wed, Mar 31, 2010 at 4:05 PM, Andrea Carlo Ornstein
<and...@gm...> wrote:
> I am sorry,
> I added the build of the library, not the use of it. :)
> That part is not done yet.
> For it I have to look in my old directories.
> But I guess it would be just a small change in
> CFileFactory.cs:LoadCFile() and CFile.cs:Save()
>
> There is a svn property 'svn:extrenals' that properly configured does
> the co of remotes svn dirs.
> I never properly checked the license from Mono for this kind of use of
> the libraries;
> and the fact that we co them and build them the way we do is really a hack.
> We should just pick the ones installed by mono on the machine.
> That's way the property is not set on trunk.
>
> But since it is really convenient I use it in my development branch :)
>
> Andrea
>
> On Wed, Mar 31, 2010 at 3:11 PM, Thierry Lafage <thi...@in...> wrote:
>> Hi Andrea,
>>
>> Great job!
>> However, I don't see how to use it... I mean how does ld merge together
>> all *.mdb files into an eg. a.out.mdb?
>> Is there any new option to use?
>> I tried on a simple example, and it didn't produce any mdb file...
>>
>> By the way, when I checkouted your branch, it automatically checkouted
>> Cecil, Cecil.Mdb and CompilerServices.SymbolWriter. It looks... magic!
>> If you can do the same for the trunk, the upgrade shouldn't be a pb.,
>> should it?
>>
>> Regards,
>>
>> Thierry Lafage.
>>
>>
>>
>> Andrea Carlo Ornstein a écrit :
>>> Hi,
>>>
>>> I ci the changes in my dev branch
>>> (https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/branches/aco-dev),
>>> it seems to be working fine.
>>>
>>> If I do the ci on trunk all the people that builds the binutils have
>>> to co two extra dirs from Mono.
>>> It will break all current checkouts.
>>>
>>> Let me know when you want me to ci on trunk.
>>>
>>> Andrea
>>>
>>>
>>> On Mon, Mar 29, 2010 at 4:26 PM, Andrea Carlo Ornstein
>>> <and...@gm...> wrote:
>>>
>>>> I am not in the office at the moment, I need a couple of days to see
>>>> what I have.
>>>> Perhaps it's already done :)
>>>> I just do not remember.
>>>>
>>>> I worked on it more than a year ago when I was writing the binutils.
>>>>
>>>> Andrea
>>>>
>>>> On Mon, Mar 29, 2010 at 3:45 PM, Thierry Lafage <thi...@in...> wrote:
>>>>
>>>>> Hi Andrea,
>>>>>
>>>>> I think that 2 more checkout points is not a problem provided that it is
>>>>> correctly documented and because there is already the dependency wrt. Cecil.
>>>>> The real problem is, I guess, how much work would it be to add this support
>>>>> and what has to be done.
>>>>> Then, given that it is not our top priority either, who should (or would be
>>>>> willing to) do the work?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Thierry Lafage.
>>>>>
>>>>>
>>>>>
>>>>> Andrea Carlo Ornstein a écrit :
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I actually tried to solve the problem a while ago,
>>>>>> after a while I give up. :)
>>>>>> It was not a priority at the time, we just would have two extra checkout
>>>>>> points.
>>>>>>
>>>>>> The right solution would be to use the libraries installed in the
>>>>>> machine you are building on (the same apply to Mono.Cecil).
>>>>>>
>>>>>> For Cecil this was always a problem, on my machine, a Debian (but also
>>>>>> on ubuntu) the library they ship is too old.
>>>>>> That is the reason we check out it from Mono repository and build it
>>>>>> from scratch.
>>>>>>
>>>>>> We can use the one installed in the machine if they are up to date
>>>>>> (small change in the e configure.ac)I can provide a patch for it.
>>>>>> OR
>>>>>> add two new checkout points and change the Makefile as I did for Cecil
>>>>>> (Imay still have may changes somewhere in my machine at the office.
>>>>>>
>>>>>> Andrea
>>>>>>
>>>>>> On Fri, Mar 26, 2010 at 6:10 PM, Thierry Lafage <thi...@in...>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Some time ago, I added .line information generation in gcc4cli so as to
>>>>>>> relate cli code to C source code. I'm preparing an ilasm patch to take
>>>>>>> these .line statements into account and write source information in the
>>>>>>> corresponding .mdb file.
>>>>>>> Now, the last stage would be to make ld gather all .mdb files together
>>>>>>> (with adequate relocation info) to build the a.out.mdb (or .dll.mdb, or
>>>>>>> ...).
>>>>>>> I've began to look at Cecil code, and I've found that there is support
>>>>>>> for mdb files in Mono.Cecil.Mdb (which have to be separately check-outed
>>>>>>> and have to include Mono.CompilerServices.SymbolWriter, also separately
>>>>>>> check-outed). But, I really don't know how to do that and whether it
>>>>>>> would be a lot of work (it seems so to me).
>>>>>>>
>>>>>>> People in this list surely have already though of this matter: what is
>>>>>>> your opinion? Would there be someone willing to develop it (maybe I
>>>>>>> would if it's not a lot of work)?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Thierry Lafage.
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Download Intel&#174; Parallel Studio Eval
>>>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>>> _______________________________________________
>>>>>>> Clibinutils-devel mailing list
>>>>>>> Cli...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>>>>>>>
>>>>>>>
>>>>>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Clibinutils-devel mailing list
>> Cli...@li...
>> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>>
>

Re: [Clibinutils-devel] Support for MDB debug info to ld

[Andrea C. O. <and...@gm...>]

I am sorry,
I added the build of the library, not the use of it. :)
That part is not done yet.
For it I have to look in my old directories.
But I guess it would be just a small change in
CFileFactory.cs:LoadCFile() and CFile.cs:Save()

There is a svn property 'svn:extrenals' that properly configured does
the co of remotes svn dirs.
I never properly checked the license from Mono for this kind of use of
the libraries;
and the fact that we co them and build them the way we do is really a hack.
We should just pick the ones installed by mono on the machine.
That's way the property is not set on trunk.

But since it is really convenient I use it in my development branch :)

Andrea

On Wed, Mar 31, 2010 at 3:11 PM, Thierry Lafage <thi...@in...> wrote:
> Hi Andrea,
>
> Great job!
> However, I don't see how to use it... I mean how does ld merge together
> all *.mdb files into an eg. a.out.mdb?
> Is there any new option to use?
> I tried on a simple example, and it didn't produce any mdb file...
>
> By the way, when I checkouted your branch, it automatically checkouted
> Cecil, Cecil.Mdb and CompilerServices.SymbolWriter. It looks... magic!
> If you can do the same for the trunk, the upgrade shouldn't be a pb.,
> should it?
>
> Regards,
>
> Thierry Lafage.
>
>
>
> Andrea Carlo Ornstein a écrit :
>> Hi,
>>
>> I ci the changes in my dev branch
>> (https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/branches/aco-dev),
>> it seems to be working fine.
>>
>> If I do the ci on trunk all the people that builds the binutils have
>> to co two extra dirs from Mono.
>> It will break all current checkouts.
>>
>> Let me know when you want me to ci on trunk.
>>
>> Andrea
>>
>>
>> On Mon, Mar 29, 2010 at 4:26 PM, Andrea Carlo Ornstein
>> <and...@gm...> wrote:
>>
>>> I am not in the office at the moment, I need a couple of days to see
>>> what I have.
>>> Perhaps it's already done :)
>>> I just do not remember.
>>>
>>> I worked on it more than a year ago when I was writing the binutils.
>>>
>>> Andrea
>>>
>>> On Mon, Mar 29, 2010 at 3:45 PM, Thierry Lafage <thi...@in...> wrote:
>>>
>>>> Hi Andrea,
>>>>
>>>> I think that 2 more checkout points is not a problem provided that it is
>>>> correctly documented and because there is already the dependency wrt. Cecil.
>>>> The real problem is, I guess, how much work would it be to add this support
>>>> and what has to be done.
>>>> Then, given that it is not our top priority either, who should (or would be
>>>> willing to) do the work?
>>>>
>>>> Regards,
>>>>
>>>> Thierry Lafage.
>>>>
>>>>
>>>>
>>>> Andrea Carlo Ornstein a écrit :
>>>>
>>>>> Hi,
>>>>>
>>>>> I actually tried to solve the problem a while ago,
>>>>> after a while I give up. :)
>>>>> It was not a priority at the time, we just would have two extra checkout
>>>>> points.
>>>>>
>>>>> The right solution would be to use the libraries installed in the
>>>>> machine you are building on (the same apply to Mono.Cecil).
>>>>>
>>>>> For Cecil this was always a problem, on my machine, a Debian (but also
>>>>> on ubuntu) the library they ship is too old.
>>>>> That is the reason we check out it from Mono repository and build it
>>>>> from scratch.
>>>>>
>>>>> We can use the one installed in the machine if they are up to date
>>>>> (small change in the e configure.ac)I can provide a patch for it.
>>>>> OR
>>>>> add two new checkout points and change the Makefile as I did for Cecil
>>>>> (Imay still have may changes somewhere in my machine at the office.
>>>>>
>>>>> Andrea
>>>>>
>>>>> On Fri, Mar 26, 2010 at 6:10 PM, Thierry Lafage <thi...@in...>
>>>>> wrote:
>>>>>
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Some time ago, I added .line information generation in gcc4cli so as to
>>>>>> relate cli code to C source code. I'm preparing an ilasm patch to take
>>>>>> these .line statements into account and write source information in the
>>>>>> corresponding .mdb file.
>>>>>> Now, the last stage would be to make ld gather all .mdb files together
>>>>>> (with adequate relocation info) to build the a.out.mdb (or .dll.mdb, or
>>>>>> ...).
>>>>>> I've began to look at Cecil code, and I've found that there is support
>>>>>> for mdb files in Mono.Cecil.Mdb (which have to be separately check-outed
>>>>>> and have to include Mono.CompilerServices.SymbolWriter, also separately
>>>>>> check-outed). But, I really don't know how to do that and whether it
>>>>>> would be a lot of work (it seems so to me).
>>>>>>
>>>>>> People in this list surely have already though of this matter: what is
>>>>>> your opinion? Would there be someone willing to develop it (maybe I
>>>>>> would if it's not a lot of work)?
>>>>>>
>>>>>> Regards,
>>>>>> Thierry Lafage.
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Download Intel&#174; Parallel Studio Eval
>>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>> _______________________________________________
>>>>>> Clibinutils-devel mailing list
>>>>>> Cli...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>>>>>>
>>>>>>
>>>>>>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Clibinutils-devel mailing list
> Cli...@li...
> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>

Re: [Clibinutils-devel] Support for MDB debug info to ld

[Thierry L. <thi...@in...>]

Hi Andrea,

Great job!
However, I don't see how to use it... I mean how does ld merge together
all *.mdb files into an eg. a.out.mdb?
Is there any new option to use?
I tried on a simple example, and it didn't produce any mdb file...

By the way, when I checkouted your branch, it automatically checkouted
Cecil, Cecil.Mdb and CompilerServices.SymbolWriter. It looks... magic!
If you can do the same for the trunk, the upgrade shouldn't be a pb.,
should it?

Regards,

Thierry Lafage.



Andrea Carlo Ornstein a écrit :
> Hi,
>
> I ci the changes in my dev branch
> (https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/branches/aco-dev),
> it seems to be working fine.
>
> If I do the ci on trunk all the people that builds the binutils have
> to co two extra dirs from Mono.
> It will break all current checkouts.
>
> Let me know when you want me to ci on trunk.
>
> Andrea
>
>
> On Mon, Mar 29, 2010 at 4:26 PM, Andrea Carlo Ornstein
> <and...@gm...> wrote:
>   
>> I am not in the office at the moment, I need a couple of days to see
>> what I have.
>> Perhaps it's already done :)
>> I just do not remember.
>>
>> I worked on it more than a year ago when I was writing the binutils.
>>
>> Andrea
>>
>> On Mon, Mar 29, 2010 at 3:45 PM, Thierry Lafage <thi...@in...> wrote:
>>     
>>> Hi Andrea,
>>>
>>> I think that 2 more checkout points is not a problem provided that it is
>>> correctly documented and because there is already the dependency wrt. Cecil.
>>> The real problem is, I guess, how much work would it be to add this support
>>> and what has to be done.
>>> Then, given that it is not our top priority either, who should (or would be
>>> willing to) do the work?
>>>
>>> Regards,
>>>
>>> Thierry Lafage.
>>>
>>>
>>>
>>> Andrea Carlo Ornstein a écrit :
>>>       
>>>> Hi,
>>>>
>>>> I actually tried to solve the problem a while ago,
>>>> after a while I give up. :)
>>>> It was not a priority at the time, we just would have two extra checkout
>>>> points.
>>>>
>>>> The right solution would be to use the libraries installed in the
>>>> machine you are building on (the same apply to Mono.Cecil).
>>>>
>>>> For Cecil this was always a problem, on my machine, a Debian (but also
>>>> on ubuntu) the library they ship is too old.
>>>> That is the reason we check out it from Mono repository and build it
>>>> from scratch.
>>>>
>>>> We can use the one installed in the machine if they are up to date
>>>> (small change in the e configure.ac)I can provide a patch for it.
>>>> OR
>>>> add two new checkout points and change the Makefile as I did for Cecil
>>>> (Imay still have may changes somewhere in my machine at the office.
>>>>
>>>> Andrea
>>>>
>>>> On Fri, Mar 26, 2010 at 6:10 PM, Thierry Lafage <thi...@in...>
>>>> wrote:
>>>>
>>>>         
>>>>> Hi all,
>>>>>
>>>>> Some time ago, I added .line information generation in gcc4cli so as to
>>>>> relate cli code to C source code. I'm preparing an ilasm patch to take
>>>>> these .line statements into account and write source information in the
>>>>> corresponding .mdb file.
>>>>> Now, the last stage would be to make ld gather all .mdb files together
>>>>> (with adequate relocation info) to build the a.out.mdb (or .dll.mdb, or
>>>>> ...).
>>>>> I've began to look at Cecil code, and I've found that there is support
>>>>> for mdb files in Mono.Cecil.Mdb (which have to be separately check-outed
>>>>> and have to include Mono.CompilerServices.SymbolWriter, also separately
>>>>> check-outed). But, I really don't know how to do that and whether it
>>>>> would be a lot of work (it seems so to me).
>>>>>
>>>>> People in this list surely have already though of this matter: what is
>>>>> your opinion? Would there be someone willing to develop it (maybe I
>>>>> would if it's not a lot of work)?
>>>>>
>>>>> Regards,
>>>>> Thierry Lafage.
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Download Intel&#174; Parallel Studio Eval
>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>> proactively, and fine-tune applications for parallel performance.
>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>> _______________________________________________
>>>>> Clibinutils-devel mailing list
>>>>> Cli...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>>>>>
>>>>>
>>>>>           

Re: [Clibinutils-devel] Support for MDB debug info to ld

[Andrea C. O. <and...@gm...>]

Hi,

I ci the changes in my dev branch
(https://clibinutils.svn.sourceforge.net/svnroot/clibinutils/mono-based-binutils/branches/aco-dev),
it seems to be working fine.

If I do the ci on trunk all the people that builds the binutils have
to co two extra dirs from Mono.
It will break all current checkouts.

Let me know when you want me to ci on trunk.

Andrea


On Mon, Mar 29, 2010 at 4:26 PM, Andrea Carlo Ornstein
<and...@gm...> wrote:
> I am not in the office at the moment, I need a couple of days to see
> what I have.
> Perhaps it's already done :)
> I just do not remember.
>
> I worked on it more than a year ago when I was writing the binutils.
>
> Andrea
>
> On Mon, Mar 29, 2010 at 3:45 PM, Thierry Lafage <thi...@in...> wrote:
>> Hi Andrea,
>>
>> I think that 2 more checkout points is not a problem provided that it is
>> correctly documented and because there is already the dependency wrt. Cecil.
>> The real problem is, I guess, how much work would it be to add this support
>> and what has to be done.
>> Then, given that it is not our top priority either, who should (or would be
>> willing to) do the work?
>>
>> Regards,
>>
>> Thierry Lafage.
>>
>>
>>
>> Andrea Carlo Ornstein a écrit :
>>>
>>> Hi,
>>>
>>> I actually tried to solve the problem a while ago,
>>> after a while I give up. :)
>>> It was not a priority at the time, we just would have two extra checkout
>>> points.
>>>
>>> The right solution would be to use the libraries installed in the
>>> machine you are building on (the same apply to Mono.Cecil).
>>>
>>> For Cecil this was always a problem, on my machine, a Debian (but also
>>> on ubuntu) the library they ship is too old.
>>> That is the reason we check out it from Mono repository and build it
>>> from scratch.
>>>
>>> We can use the one installed in the machine if they are up to date
>>> (small change in the e configure.ac)I can provide a patch for it.
>>> OR
>>> add two new checkout points and change the Makefile as I did for Cecil
>>> (Imay still have may changes somewhere in my machine at the office.
>>>
>>> Andrea
>>>
>>> On Fri, Mar 26, 2010 at 6:10 PM, Thierry Lafage <thi...@in...>
>>> wrote:
>>>
>>>>
>>>> Hi all,
>>>>
>>>> Some time ago, I added .line information generation in gcc4cli so as to
>>>> relate cli code to C source code. I'm preparing an ilasm patch to take
>>>> these .line statements into account and write source information in the
>>>> corresponding .mdb file.
>>>> Now, the last stage would be to make ld gather all .mdb files together
>>>> (with adequate relocation info) to build the a.out.mdb (or .dll.mdb, or
>>>> ...).
>>>> I've began to look at Cecil code, and I've found that there is support
>>>> for mdb files in Mono.Cecil.Mdb (which have to be separately check-outed
>>>> and have to include Mono.CompilerServices.SymbolWriter, also separately
>>>> check-outed). But, I really don't know how to do that and whether it
>>>> would be a lot of work (it seems so to me).
>>>>
>>>> People in this list surely have already though of this matter: what is
>>>> your opinion? Would there be someone willing to develop it (maybe I
>>>> would if it's not a lot of work)?
>>>>
>>>> Regards,
>>>> Thierry Lafage.
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Download Intel&#174; Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> Clibinutils-devel mailing list
>>>> Cli...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>>>>
>>>>
>>
>

Re: [Clibinutils-devel] Support for MDB debug info to ld

[Andrea C. O. <and...@gm...>]

I am not in the office at the moment, I need a couple of days to see
what I have.
Perhaps it's already done :)
I just do not remember.

I worked on it more than a year ago when I was writing the binutils.

Andrea

On Mon, Mar 29, 2010 at 3:45 PM, Thierry Lafage <thi...@in...> wrote:
> Hi Andrea,
>
> I think that 2 more checkout points is not a problem provided that it is
> correctly documented and because there is already the dependency wrt. Cecil.
> The real problem is, I guess, how much work would it be to add this support
> and what has to be done.
> Then, given that it is not our top priority either, who should (or would be
> willing to) do the work?
>
> Regards,
>
> Thierry Lafage.
>
>
>
> Andrea Carlo Ornstein a écrit :
>>
>> Hi,
>>
>> I actually tried to solve the problem a while ago,
>> after a while I give up. :)
>> It was not a priority at the time, we just would have two extra checkout
>> points.
>>
>> The right solution would be to use the libraries installed in the
>> machine you are building on (the same apply to Mono.Cecil).
>>
>> For Cecil this was always a problem, on my machine, a Debian (but also
>> on ubuntu) the library they ship is too old.
>> That is the reason we check out it from Mono repository and build it
>> from scratch.
>>
>> We can use the one installed in the machine if they are up to date
>> (small change in the e configure.ac)I can provide a patch for it.
>> OR
>> add two new checkout points and change the Makefile as I did for Cecil
>> (Imay still have may changes somewhere in my machine at the office.
>>
>> Andrea
>>
>> On Fri, Mar 26, 2010 at 6:10 PM, Thierry Lafage <thi...@in...>
>> wrote:
>>
>>>
>>> Hi all,
>>>
>>> Some time ago, I added .line information generation in gcc4cli so as to
>>> relate cli code to C source code. I'm preparing an ilasm patch to take
>>> these .line statements into account and write source information in the
>>> corresponding .mdb file.
>>> Now, the last stage would be to make ld gather all .mdb files together
>>> (with adequate relocation info) to build the a.out.mdb (or .dll.mdb, or
>>> ...).
>>> I've began to look at Cecil code, and I've found that there is support
>>> for mdb files in Mono.Cecil.Mdb (which have to be separately check-outed
>>> and have to include Mono.CompilerServices.SymbolWriter, also separately
>>> check-outed). But, I really don't know how to do that and whether it
>>> would be a lot of work (it seems so to me).
>>>
>>> People in this list surely have already though of this matter: what is
>>> your opinion? Would there be someone willing to develop it (maybe I
>>> would if it's not a lot of work)?
>>>
>>> Regards,
>>> Thierry Lafage.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel&#174; Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Clibinutils-devel mailing list
>>> Cli...@li...
>>> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>>>
>>>
>

Re: [Clibinutils-devel] Support for MDB debug info to ld

[Thierry L. <thi...@in...>]

Hi Andrea,

I think that 2 more checkout points is not a problem provided that it is 
correctly documented and because there is already the dependency wrt. Cecil.
The real problem is, I guess, how much work would it be to add this 
support and what has to be done.
Then, given that it is not our top priority either, who should (or would 
be willing to) do the work?

Regards,

Thierry Lafage.



Andrea Carlo Ornstein a écrit :
> Hi,
>
> I actually tried to solve the problem a while ago,
> after a while I give up. :)
> It was not a priority at the time, we just would have two extra checkout points.
>
> The right solution would be to use the libraries installed in the
> machine you are building on (the same apply to Mono.Cecil).
>
> For Cecil this was always a problem, on my machine, a Debian (but also
> on ubuntu) the library they ship is too old.
> That is the reason we check out it from Mono repository and build it
> from scratch.
>
> We can use the one installed in the machine if they are up to date
> (small change in the e configure.ac)I can provide a patch for it.
> OR
> add two new checkout points and change the Makefile as I did for Cecil
> (Imay still have may changes somewhere in my machine at the office.
>
> Andrea
>
> On Fri, Mar 26, 2010 at 6:10 PM, Thierry Lafage <thi...@in...> wrote:
>   
>> Hi all,
>>
>> Some time ago, I added .line information generation in gcc4cli so as to
>> relate cli code to C source code. I'm preparing an ilasm patch to take
>> these .line statements into account and write source information in the
>> corresponding .mdb file.
>> Now, the last stage would be to make ld gather all .mdb files together
>> (with adequate relocation info) to build the a.out.mdb (or .dll.mdb, or
>> ...).
>> I've began to look at Cecil code, and I've found that there is support
>> for mdb files in Mono.Cecil.Mdb (which have to be separately check-outed
>> and have to include Mono.CompilerServices.SymbolWriter, also separately
>> check-outed). But, I really don't know how to do that and whether it
>> would be a lot of work (it seems so to me).
>>
>> People in this list surely have already though of this matter: what is
>> your opinion? Would there be someone willing to develop it (maybe I
>> would if it's not a lot of work)?
>>
>> Regards,
>> Thierry Lafage.
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Clibinutils-devel mailing list
>> Cli...@li...
>> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>>
>>     

Re: [Clibinutils-devel] Support for MDB debug info to ld

[Andrea C. O. <and...@gm...>]

Hi,

I actually tried to solve the problem a while ago,
after a while I give up. :)
It was not a priority at the time, we just would have two extra checkout points.

The right solution would be to use the libraries installed in the
machine you are building on (the same apply to Mono.Cecil).

For Cecil this was always a problem, on my machine, a Debian (but also
on ubuntu) the library they ship is too old.
That is the reason we check out it from Mono repository and build it
from scratch.

We can use the one installed in the machine if they are up to date
(small change in the e configure.ac)I can provide a patch for it.
OR
add two new checkout points and change the Makefile as I did for Cecil
(Imay still have may changes somewhere in my machine at the office.

Andrea

On Fri, Mar 26, 2010 at 6:10 PM, Thierry Lafage <thi...@in...> wrote:
> Hi all,
>
> Some time ago, I added .line information generation in gcc4cli so as to
> relate cli code to C source code. I'm preparing an ilasm patch to take
> these .line statements into account and write source information in the
> corresponding .mdb file.
> Now, the last stage would be to make ld gather all .mdb files together
> (with adequate relocation info) to build the a.out.mdb (or .dll.mdb, or
> ...).
> I've began to look at Cecil code, and I've found that there is support
> for mdb files in Mono.Cecil.Mdb (which have to be separately check-outed
> and have to include Mono.CompilerServices.SymbolWriter, also separately
> check-outed). But, I really don't know how to do that and whether it
> would be a lot of work (it seems so to me).
>
> People in this list surely have already though of this matter: what is
> your opinion? Would there be someone willing to develop it (maybe I
> would if it's not a lot of work)?
>
> Regards,
> Thierry Lafage.
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Clibinutils-devel mailing list
> Cli...@li...
> https://lists.sourceforge.net/lists/listinfo/clibinutils-devel
>

[Clibinutils-devel] Support for MDB debug info to ld

[Thierry L. <thi...@in...>]

Hi all,

Some time ago, I added .line information generation in gcc4cli so as to 
relate cli code to C source code. I'm preparing an ilasm patch to take 
these .line statements into account and write source information in the 
corresponding .mdb file.
Now, the last stage would be to make ld gather all .mdb files together 
(with adequate relocation info) to build the a.out.mdb (or .dll.mdb, or 
...).
I've began to look at Cecil code, and I've found that there is support 
for mdb files in Mono.Cecil.Mdb (which have to be separately check-outed 
and have to include Mono.CompilerServices.SymbolWriter, also separately 
check-outed). But, I really don't know how to do that and whether it 
would be a lot of work (it seems so to me).

People in this list surely have already though of this matter: what is 
your opinion? Would there be someone willing to develop it (maybe I 
would if it's not a lot of work)?

Regards,
Thierry Lafage.