taskSavannah Administration - Tasks: task #4192, Submission of pDI-Tools

 
 

task #4192: Submission of pDI-Tools

Submitter:  Gerardo García Peña <killabyte>
Submitted:  Fri 27 May 2005 04:36:26 PM UTC
   
 
Should Start On:  Fri 27 May 2005 12:00:00 AM UTC Should be Finished on:  Mon 06 Jun 2005 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  kickino Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Fri 03 Jun 2005 11:22:27 PM UTC, comment #7: 

Hi!

I will correct now the copyright notices in 'README', 'missing', 'depcomp'.

But 'include/datadir.h' is an automatic generated file,
while 'config-sub' and 'config.guess' are part of Autoconf and Automake :(

Thanks for your approving!!

  Gerardo García Peña

Gerardo García Peña <killabyte>
Fri 03 Jun 2005 10:32:23 PM UTC, comment #6: 

Hi,

I have approved your project.  You will receive an automated e-mail containing detailed information about the approval.


But anyway you should add a copyright notice in 'include/datadir.h' and update the FSF address in 'README', 'missing', 'depcomp', 'config-sub' and 'config.guess'.
Thanks.

Sebastian Wieseler <kickino>
Fri 03 Jun 2005 12:17:20 AM UTC, comment #5: 

Hi!

I updated the address of the FSF everywhere, and also I updated all licenses (included the FDL Appendix on my doc). I don't know where I got them, but some were pretty old :)

I have added a new directory /licenses with all licenses I have used in pDI-Tools. I have added GPL because I decided to put some little Perl scripts and a makefile under GPL instead of LGPL (all these are used to build the doc, Perl is not required to build pDI-Tools).

I have added a new COPYING file. Now I have two COPYING files, one at root directory with the LGPL (the main license) and another in /doc directory with the FDL.

I have uploaded all changes to
   http://kung-foo.dhs.org/killabyte/pdi/

the file pdi-tools-0.1.0.tar.gz is also rebuilt.

Looking forward for your response,
  Gerardo

Gerardo García Peña <killabyte>
Wed 01 Jun 2005 08:29:14 PM UTC, comment #4: 

Hello again. :)

The address of the FSF has changed, and is now:

  51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA

Please update your license notices.

Updates versions of the GPL, LGPL and GFDL can also be found at:
http://www.gnu.org/licenses/gpl.txt
http://www.gnu.org/licenses/lgpl.txt
http://www.gnu.org/licenses/fdl.txt

Please update the copy of the license (usually, the 'COPYING' file) in your package as well.

You can find some background and a possible migration script at https://savannah.gnu.org/forum/forum.php?forum_id=3766

Thanks.

Sebastian Wieseler <kickino>
Wed 01 Jun 2005 07:59:53 PM UTC, comment #3: 

Hello.

For your documenation files:
In order to release your project properly and unambiguously under the FDL, please place copyright notices and permission-to-copy statements after the title page of each work.

In addition, if you haven't already, please copy a copy
of the plain text version of the FDL, available from
http://www.gnu.org/licenses/fdl.txt, into a file named "COPYING".

For more information, see http://www.gnu.org/licenses/fdl.html.


And please update your files:
The address of the FSF has changed, and is now:

  59 Temple Place, Suite 330 Boston, MA 02111-1307 USA


Regards,

Sebastian Wieseler <kickino>
Sun 29 May 2005 12:44:54 PM UTC, comment #2: 


> Hi,
> I'm evaluating the project you submitted for approval in
> Savannah.


> Note that we do not want to encourage software primarily aimed
> at cracking purposes. Would you mind telling us what is the
> primary purpose of the software?


NO! It's is  not for cracking purposes! It is one of its possible uses because it is very powerful. And, in spite of we like it or not, it can be used for that purpose.

Its primary target is super computing: instrumentation of code at runtime. It has been coded for making performance evaluation on scientific programs on multis and clusters. Its first mission would be tracing MPI communications and show them graphically with all details.  I will try to make it debut at Marenostrum [1]. Marenostrum is a supercomputer made of IBM PowerPC Server Blades running GNU/Linux. It is part of BSC [2] (Barcelona Supercomputer Center).

I have coded pDI-Tools for CEPBA [3] (CEPBA will be probably assimilated by BSC in the near future). They have a dynamic instrumentation program called DI-Tools, but it is not so powerful as pDI-Tools. I have write pDI-Tools from zero and all copyright is mine, and I have decided to put it under a LGPL license.

The original DI-Tools only run on Irix with MIPS and it is not portable, while pDI-Tools run on a lot of a platforms and it is very portable.

pDI-Tools is designed as a replacement for DI-Tools. DI-Tools is the base of a lot of programs of CEPBA, for instance PARAVER [4] and DIMEMAS [5]. Both are graphical interpreters of the data collected by an instrumentation program called OMPItrace, which is built on top DI-Tools. Making a free pDI-Tools can motivate CEPBA to free its software in the future or can be the base of future free instrumentation software.

Currently there is only one Open Source Dynamic Instrumentation API: Dyninst [6]. Dyninst is NOT FREE. And it is currently the only option. The most similar free software I have found is Elfsh [7] (that can be also used for cracking  ;) ). It is possible to write a instrumentation software on Elfsh, but this is not the primary objective of Elfsh. Elfsh is more oriented to debug ELF structures
and playing with them on runtime, so it can do more powerful modifications but it is also more difficult to port to another archs (it only runs on Sparc 32 (¿64?) and i386, while pDI-Tools run on i386, PPC, PPC64, SPARC32, SPARC64, MIPS N32 & MIPS 64).

So I think that it is necesary to fill this hole at free software giving a tool such pDI-Tools.

In the other hand pDI-Tools can be used to make execution drive simulations. For instance with pDI-Tools you can substitute some code with your own code. Your new code can intercept some critical funcs as open, read, write, etc... and make them fail sometimes. Doing this you can check the robustness of your
program in a very unfavorable scenario. So it is not only useful for supercomputer labs.

[1] Marenostrum TOP500: http://top500.org/sublist/System.php?id=7119
[2] Barcelona Supercomputer Center: http://www.bsc.org.es/
[3] CEPBA: http://www.cepba.upc.es/
[4] PARAVER: http://www.cepba.upc.edu/paraver/
[5] DIMEMAS: http://www.cepba.upc.edu/dimemas/
[6] Dyninst: http://www.dyninst.org/
[7] Elfsh: http://elfsh.segfault.net/

> Please include a (perhaps temporary) URL pointing to
> the source code.
>
> We wish to review your source code, even if it is not
> functional, to catch potential legal issues early.


If you want I can send you a .tar.gz with all code and docs, but remember that this version is too preliminar to show it to the public. It is a very early version and it is not very stable.

If you only want to see the source code you can find it at:
    http://kung-foo.dhs.org/killabyte/pdi/

the principal sources are in
    http://kung-foo.dhs.org/killabyte/pdi/src/link

I am worried about legal problems so I wrote all from scratch without looking to any program except gdb and glibc.

> For example, to release your program properly under the GPL you
> must include a copyright notice and permission-to-copy
> statements at the beginning of every file of source code. This
> is explained in
> http://www.gnu.org/licenses/gpl-howto.html.
> Our review would help catch potential omissions such as these.


Thanks, I will read it, but already I included the legal notice  ;)

My best regards,
    Gerardo García Peña

Gerardo García Peña <killabyte>
Sat 28 May 2005 05:47:36 PM UTC, comment #1: 

Hi,
I'm evaluating the project you submitted for approval in Savannah.


Note that we do not want to encourage software primarily aimed at
cracking purposes. Would you mind telling us what is the primary purpose of the software?

Please include a (perhaps temporary) URL pointing to
the source code.
We wish to review your source code, even if it is not functional, to catch potential legal issues early.

For example, to release your program properly under the GPL you must include a copyright notice and permission-to-copy statements at the beginning of every file of source code.  This is explained in
http://www.gnu.org/licenses/gpl-howto.html.
Our review would help catch potential omissions such as these.

Regards,

Sebastian Wieseler <kickino>
Fri 27 May 2005 04:36:26 PM UTC, original submission:  


Site Admin. Approval/Edition URL:
 <https://savannah.gnu.org/admin/groupedit.php?group_id=7663>


###### ORIGINAL SUBMISSION DETAILS ######

System Group Name:
-----------------
  pditools


Full Name:
----------
  pDI-Tools


Type:
-----
  non-GNU software & documentation


License:
--------
  GNU Lesser General Public License


Other License:
--------------



Description:
------------
  pDI-Tools is a very powerful and portable API and engine that can be used to create dynamic instrumentation tools, performance tools, execution drive simulations, reverse engineering, hacking, play with binary executables, and a lot more. Its main features are portability, ease of use, compact and fast. It works with any executable, even with binaries without debug information or source code.

It implements mechanisms based on intercepting calls between dynamic shared objects (executable-libraries, libraries-libraries). These mechanisms exploit ELF structures and data, making them very efficient and portable. It currently works on GNU/Linux (i386, PowerPC, PowerPC 64), Solaris (SPARC 32 and 64 bits) and Irix (MIPS 32 and 64).


Other Software Required:
------------------------
  It only needs a make program and a C compiler (preferently GNU Make and GNU C).

This program uses Autoconf, Automake for creating the building and installation system.

Docbook/XSL is used for documentation but I provide pre-rendered doc in HTML, PS and PDF.


Other Comments:
---------------


#########################################

Gerardo García Peña <killabyte>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 7 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2005-06-03 kickino StatusWait reply Done
    Open/ClosedOpen Closed
2005-05-28 kickino StatusNone Wait reply
    Assigned toNone kickino
    Carbon-Copy- Added frank_org
    Carbon-Copy- Added sv-opening
    Carbon-Copy- Added killabyte

Back to the top

Powered by Savane 3.13-4448.
Corresponding source code