From ivosh@ivosh.net Fri Oct 13 10:47:00 2017 From: ivosh@ivosh.net (Ivo Raisr) Date: Fri, 13 Oct 2017 10:47:00 -0000 Subject: [FOSDEM] Call for Participation: Debugging Tools DevRoom at FOSDEM 2018 Message-ID: Debugging Tools developer room at FOSDEM 2018 (Brussels, Belgium, February 3th). FOSDEM is a free software event that offers open source communities a place to meet, share ideas and collaborate. It is renown for being highly developer-oriented and brings together 5000+ hackers from all over the world. It is held in the city of Brussels (Belgium). http://fosdem.org/ FOSDEM 2018 will take place during the weekend of Saturday, February 3th and Sunday February 4th 2018. On Saturday we will have a devroom for Debugging Tools, jointly organized by the Valgrind and GDB projects. Devrooms are a place for development teams to meet, discuss, hack and publicly present the project's latest improvements and future directions. We will have a whole day to hang out together as community embracing debugging tools, such as Valgrind, gdb, RR, Infinity, radare... Please join us, regardless of whether you are a core hacker, a plugin hacker, a user, a packager or a hacker on a project that integrates, extends or complements debugging tools. ** Call for Participation We would like to organize a series of talks/discussions on various topics relevant to both core hackers, new developers, users, packagers and cross project functionality. Please do submit a talk proposal by Friday December 1st 2017, so we can make a list of activities during the day. Some possible topics for talks/discussions are: - The recently added functional changes (for users). - Get feedback on what what kinds of new functionality would be useful. Which tools and functionality users would like to see. - Discuss release/bugfixing strategy/policy (core hackers, packagers). - Connecting debugging tools together. - Latest DWARF extensions, going from binary back to source. - Multi, multi, multi... threads, processes and targets. - Debugging anything, everywhere. Dealing with complex systems. - Dealing with the dynamic loader and the kernel. - Intercepting and interposing functions and events. - Adding GDB features, such as designing GDB python scripts for your data structures. - Advances in gdbserver and the GDB remote serial protocol. - Adding Valgrind features (adding syscalls for a platform or VEX instructions for an architecture port). - Infrastructure changes to the Valgrind JIT framework. - Your interesting use case with a debugging tool. ** How to Submit There are two ways. The first one is to use the FOSDEM 'pentabarf' tool to submit your proposal: https://penta.fosdem.org/submission/FOSDEM18 - If necessary, create a Pentabarf account and activate it. Please reuse your account from previous years if you have already created it. - In the "Person" section, provide First name, Last name (in the "General" tab), Email (in the "Contact" tab) and Bio ("Abstract" field in the "Description" tab). - Submit a proposal by clicking on "Create event". - Important! Select the "Debugging Tools devroom" track (on the "General" tab). - Provide the title of your talk ("Event title" in the "General" tab). - Provide a description of the subject of the talk and the intended audience (in the "Abstract" field of the "Description" tab) - Provide a rough outline of the talk or goals of the session (a short list of bullet points covering topics that will be discussed) in the "Full description" field in the "Description" tab The second way is to email your talk proposal to valgrind-devroom-manager@fosdem.org alias. Julian, Philippe, Mark, Ivosh, and Pedro will review the proposals and organize the schedule for the day. Please feel free to suggest or discuss any ideas for the devroom on valgrind-devroom-manager@fosdem.org alias. ** Recording of Talks As usually the FOSDEM organisers plan to have live streaming and recording fully working, both for remote/later viewing of talks, and so that people can watch streams in the hallways when rooms are full. This obviously requires speakers to consent to being recorded and streamed. If you plan to be a speaker, please understand that by doing so you implicitly give consent for your talk to be recorded and streamed. The recordings will be published under the same licence as all FOSDEM content (CC-BY). Important dates: Talk/Discussion Submission deadline: Friday 1 Dec 2017 Devroom Schedule announcement: Friday 15 Dec 2017 Devroom day: Saturday 3 Feb 2018 Hope to see you all at FOSDEM 2018 in the joint Debugging Tools devroom. Brussels (Belgium), Saturday February 3th 2018. On behalf of the devroom committee, Ivo Raisr From gbenson@redhat.com Tue Oct 31 20:35:00 2017 From: gbenson@redhat.com (Gary Benson) Date: Tue, 31 Oct 2017 20:35:00 -0000 Subject: libi8x 0.0.5 released Message-ID: <20171031203530.GA21096@blade.nx> libi8x 0.0.5 released! Release 0.0.5 of libi8x, the Infinity Runtime Library, is now available. You can download the source from infinitynotes.org: https://infinitynotes.org/src/libi8x/libi8x-0.0.5.tar.xz (md5sum e9ac85a90fe9b878b0390bd7b1fdd899) You can build from source using the usual ./configure, make process, or, on rpm-based systems you *may* be able to build rpms straight from the tarball: rpmbuild -ta libi8x-0.0.5.tar.xz (Let me know if there's a Debian/Ubuntu equivalent, I'll add it!) libi8x 0.0.5 brings new features and improvements, including: * The shared library libi8x.so is now versioned, and a number of symbols have been made internal in preparation for a 1.0 release. The soname has been changed from libi8x.so.0 to libi8x.so.1 to reflect this. * libi8x now has Python bindings, and tests may now be written using Python or C. * The debug interpreter defaults to on if log level >= LOG_DEBUG when the execution context is created, so it's no longer necessary to set I8X_DEBUG to see trace messages. * The I8X_DEBUG environment variable has been renamed as I8X_DBG_MEM to reflect the fact that it now has a single purpose (enabling the debug allocator). * libi8x now supports local functions. These are native functions registered with a zero-length provider; they may be accessed by reference but not by name. Essentially they are anonymous functions with optional names. For a complete list and more details on each item, please see the NEWS file. Please note that the Python bindings have a separate release schedule from libi8x. They're shipped in the main libi8x tarball (to run the testsuite) but regular users should use the versioned releases from https://infinitynotes.org/src/libi8x-python or PyPI. -- https://infinitynotes.org/ From gbenson@redhat.com Tue Oct 31 20:40:00 2017 From: gbenson@redhat.com (Gary Benson) Date: Tue, 31 Oct 2017 20:40:00 -0000 Subject: libi8x-python 0.0.1 released Message-ID: <20171031204016.GB21096@blade.nx> libi8x-python 0.0.1 released! Release 0.0.1 of libi8x-python, Python bindings for the Infinity Runtime Library, is now available. libi8x-python requires you to have libi8x installed on your system. Once that's done you can install libi8x-python directly using pip: pip install -U --user libi8x-python # installs in your home directory sudo pip install -U libi8x-python # installs as root The source is available from infinitynotes.org: https://infinitynotes.org/src/libi8x-python/libi8x-python-0.0.1.tar.xz (md5sum 52ab73bc88bec7b4c39481410b56e605) -- https://infinitynotes.org/ From gbenson@redhat.com Thu Nov 2 13:57:00 2017 From: gbenson@redhat.com (Gary Benson) Date: Thu, 02 Nov 2017 13:57:00 -0000 Subject: I8C 0.0.6 released Message-ID: <20171102135750.GA32115@blade.nx> I8C 0.0.6 released! Release 0.0.6 of I8C, the Infinity Note Compiler, is now available. This includes I8X, an interpreter for unit testing compiled notes. You can install I8C and I8X directly using pip: pip install -U --user i8c # installs in your home directory sudo pip install -U i8c # installs as root The source is available from infinitynotes.org: https://infinitynotes.org/src/i8c/i8c-0.0.6.tar.xz (md5sum ad321c0cf08f49d54b19113692877796) There is a web page for I8C at: https://infinitynotes.org/wiki/I8C That page includes information about the Infinity mailing list, details on how to access I8C's source repository, and information about the Infinity system in general. I8C 0.0.6 brings new features and improvements, including: * I8X will now use libi8x to execute Infinity functions if libi8x and its Python bindings are installed. The original Python interpreter has been retained as a fallback but will be removed in a future I8C release. * I8X now correctly determines names for referenced symbols in many more configurations, and now fails gracefully when names cannot be determined. * Infinity functions provided by testcases are now identified using the @TestCase.provide decorator. The function TestCase.implement has been removed. * The interpreter context is no longer accessible as TestCase.i8ctx. Infinity functions should now be executed using TestCase.call. * TestCase.warn_caller is now called with two arguments, the first being the signature of the Infinity function emitting the warning and the second being the warning message as before. For a complete list and more details on each item, please see the NEWS.rst file. -- https://infinitynotes.org/