[Caml-list] Call for Paper for HotSWUp 2011: Third Workshop on Hot Topics in Software Upgrades
The following call for paper may be of interest to some members of the function community. The submission site is now open and the deadline is in 2 weeks Fabien Dagnat CALL FOR PAPERS HotSWUp 2011: Third Workshop on Hot Topics in Software Upgrades (co-located with ICDE 2011) Hannover, Germany April 16, 2011 http://www.hotswup.org Submission deadline: 15 November 2010 OBJECTIVES Actively-used software systems are upgraded regularly to incorporate bug fixes and security patches or to keep up with the evolving requirements. Whether upgrades are applied offline or online, they significantly impact the system's performance and reliability. Recently-introduced commercial products aim to address various aspects of this problem; however, recent studies and a large body of anecdotal evidence suggest that upgrades remain failure-prone, tedious, and expensive. The goal of the HotSWUp Workshop is to identify cutting-edge research for supporting software system upgrades that are flexible, efficient, robust, and easy to specify and apply. Many diverse research areas are concerned with building large, evolving, highly-available systems. As such, HotSWUp seeks contributions from all these areas, ranging from databases to distributed systems, and from programming languages to software engineering, and separately reflected in conferences such as SIGMOD, ICDE, SOSP, OSDI, OOPSLA, PLDI, ICSE, and FSE. By seeking contributions from both academic researchers and industry practitioners, HotSWUp aims to combine novel ideas with experience from upgrading real systems. The present workshop aims to build on the successes of HotSWUp'08 and HotSWUp'09 where the paper presentations and lively discussions attracted a diverse audience of researchers. The topics of interest include, but are not limited to: - Upgrading Information Systems under Schema Evolution. - Programming language / operating system / database support for software upgrades. - Improving the reliability of upgrades (e.g., support for upgrade validation and for rollback after failures). - Support for system or data restructuring (e.g., evolving APIs, changes to database schemas). - Identifying dependencies between components and guaranteeing safe interactions among mixed versions. - Coordinating and disseminating upgrades in large-scale distributed systems. - Software upgrades and the Cloud Computing Infrastructure. - Tools for preparing, testing, and applying software upgrades. - Human factors in software upgrades (e.g., usability of upgrading tools, common operator mistakes). SUBMISSION GUIDELINES We are interested in papers that address practical as well as theoretical aspects of software upgrades from large scale to embedded applications. Particularly welcome this year are submissions concerning software upgrade issues in database systems. Preferably, submissions should fall into one of the following categories: - Suggest how a successful approach can be applied in a different context (e.g., static dependency analysis applied to distributed-system upgrades). - Refute an old assumption about software upgrades (e.g., by presenting negative results). - Describe a new problem or propose a novel solution to an old problem. - Present empirical evidence related to the practical implementation of software upgrades. Papers must not exceed 5 pages, in IEEE camera-ready format (templates at http://www.ieee.org/web/publications/pubservices/confpub/AuthorTools/...). Papers must be submitted electronically at http://www.hotswup.org. IMPORTANT DATES Submission deadline 15 November 2010 Acceptance notification 15 December 2010 Camera-ready deadline 3 January 2011 Workshop date 16 April 2011 PROGRAM COMMITTEE Rida Bazzi, Arizona State University, USA (co-organizer) Carlo Aldo Curino, Massachusetts Institute of Technology, USA Fabien Dagnat, Telecom Bretagne, France Johann Eder, University of Vienna, Austria Michael Hicks, University of Maryland, College park, USA (co-organizer) Manuel Oriol, University of York, UK George Papastefanatos, National Technical University of Athens, Greece Paolo Papotti, Università Roma Tre, Italy Jason Nieh, Columbia University, USA Xin Qi, Facebook, USA Mark Segal, Laboratory for Telecommunications Sciences, USA Liuba Shrira, Brandeis University, USA Carlo Zaniolo, University of California, Los Angeles, USA (co-organizer) MORE INFORMATION Visit the workshop's homepage at: http://www.hotswup.org ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug report
Re: [Caml-list] (Announce) "OCAPIC" : OCaml for PIC18 microcontrollers
Interesting project. Was the choice of PIC based on technical reasons or just familiarity of the authors with these chips ? I would have liked to give it a try but unfortunately I work AVRs and avr-gcc. Best, Daniel ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
Re: [Caml-list] Merging object signatures
Hi, > Can't you make foo_t and bar_t class types and foobar_t inherits them > both? Thanks for the reply. Yes, in the toy example I posted that would indeed be an alternative. Still, I'm wondering about the most general case; suppose I had a function that took an object satisfying both foo_t and bar_t: val do_something: < foo_t; bar_t; .. > -> bool This is what I'm wondering if it's possible to express. Best regards, Dario Teixeira ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
Re: [Caml-list] (Announce) "OCAPIC" : OCaml for PIC18 microcontrollers
PIC ASM is the first "programming language" Benoît learnt, a few years ago. He has practiced it ever since. But meanwhile he learnt OCaml (among other languages). A few months ago, he suggested me to implement an OCaml virtual machine running on PICs, with maximum performance efficiency in mind. This is why OCAPIC's VM is implemented in ASM. The purpose is of course to program PICs with a high level language while remaining (relatively) *very* efficient. Vincent St-Amour and Marc Feeley have a similar project (Scheme on PICs) which a much higher priority on portability: their VM is implemented in C code. http://www.ccs.neu.edu/home/stamourv/picobit-ifl.pdf The "side effect" of our project — which can interest many OCaml users — is that OCAPIC provides "ocamlclean", which is a tool that takes an OCaml bytecode binary (produced by ocamlc) and reduces it by (statically) eliminating most of its deadcode (and of course dynlink is thence broken; note that dynlink is not relevant on PICs). This tool is independent from the rest of OCAPIC. Actually, this tool was mandatory for programs using OO-layer : without it, bytecode binaries embedding OO-layer were to big to fit on our PICs. Cheers, Philippe On Nov 5, 2010, at 1:35 PM, Daniel Bünzli wrote: > Interesting project. Was the choice of PIC based on technical reasons > or just familiarity of the authors with these chips ? > > I would have liked to give it a try but unfortunately I work AVRs and avr-gcc. > > Best, > > Daniel ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
Re: [Caml-list] Merging object signatures
On 2010/11/05, at 21:58, Dario Teixeira wrote: >> Can't you make foo_t and bar_t class types and foobar_t inherits them >> both? > > Thanks for the reply. Yes, in the toy example I posted that would indeed > be an alternative. Still, I'm wondering about the most general case; > suppose I had a function that took an object satisfying both foo_t and bar_t: > > val do_something: < foo_t; bar_t; .. > -> bool > > This is what I'm wondering if it's possible to express. Same thing: class type foobar_t = object inherit foo_t inherit bar_t end val do_something : #foobar_t -> bool I agree that this is rather verbose. I thought a few times of adding the syntax you propose, but was always stopped by the fact you can already do it in a verbose way. Jacques Garrigue ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
Re: [Caml-list] Causes for segfaults
Hello, 2010/11/4 Jamie Brandon : > The unmarshalling itself finishes ok but I guess the > segfault could be caused when accessing the resulting data structure? You could frequently call major collection in the GC, in order to be as close as possible to the source of the segfault (e.g. after your unmarshalling). Sincerely yours, david ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
Re: [Caml-list] rpc: type conversion
On Thu, Nov 4, 2010 at 2:26 PM, Philippe Strauss wrote: > I need to use RPC in a current project of mine, but I don't get how do you > write the type conversion and what is provided, taking a very basic example: > If you are using OCaml on both ends, you might prefer to use orpc: http://jaked.github.com/orpc/ which generates stubs from OCaml signatures rather than ONC RPC interface files. Jake ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
Re: [Caml-list] Merging object signatures
Hi, > class type foobar_t = object inherit foo_t inherit bar_t end > val do_something : #foobar_t -> bool > > I agree that this is rather verbose. I thought a few times of adding the > syntax you propose, but was always stopped by the fact you can already do > it in a verbose way. Actually, I was unaware that the '#' syntax could also be used for objects, though in retrospect it does make sense given how its used with polymorphic variants. And verboseness notwithstanding, the code above does solve my problem nicely -- thanks! Best regards, Dario Teixeira ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
[Caml-list] mobilité : un chantier prioritair e pour Attali, négocié par les syndicats
Présentation loi mobilité du 5/11/10mobilité : un chantier prioritaire pour Attali, négocié par les syndicatsFichier complet à retrouver dans le dossier dernière actualité du 5/11/10 ainsi que tous les autres dont le résumé de la loi mobilité ; cliquer sur dowload à gauche puis récupérer le fichier en bas à droite. Supprimer l'espace entre les deux caractère s s'il apparaissait en recopiant dans la barre d'adresse. Dans la mesure où les envois sont parfois interceptés, vous pouvez consulter les actualités mobilités sur :http://www.box.net/shared/rr7x4aood6Un rapport du Sénat enquête : le pari de la RGPP paraît en passe d'être perdu car dans les préfectures, on est arrivé à l'os ou encore on fait tourner un moteur sans hu ile ; qu'à cela ne tienne pour le rapport Attali la mobilité constitue le chantier prioritaire, cela n'a que trop duré ;le 15/10/10, la Commission Attali a rendu son rapport :D'autres chantiers que la Commission a identifiés comme prioritaires ont fait l'objet de réalisations limitées la mobilité géographique et socialeConformément aux directives de la commission européenne :il convi ent notamment de favoriser la mobilité professionnelle entre les régions et entre les emplois dans le cadre d'un dialogue constructif avec les partenaires sociauxMessage entendu, les fédérations de fonctionnaires négocient actuellement : les procédures.. de mobilité des fonctionnaires selon Georges Tron lui-même selon les termes de sa lettre du 18/10/10.Chatel a envoyé,avec la fiche de paye de septembre, le pacte de carrière à tous les enseignants du primaire et du secondaire, antichambre de la loi mobilité tandis que les académies organisent les réunions mobilité pour la reconversion et & eacute;tablir les CV .Mais pas si simple, alors que l'UGFF CGT se prononçait encore pour l'abrogation de la loi mobilité en septembre, tout en allant négocier, FO DGFIP ( impôt et trésor) vote à son congrès le 22/10/10 l'abrogation de la loi mobilité et le retrait du décret de réorientation professionnel alors que la FGF FO est en train de le négocier.Pour circonscrire cette résistance, dès le 3/11/2010, la direction PCF du SNES syndicat majoritaire chez les enseignants du secondaire exige l'application de la loi mobilité à travers le pacte de carrière dans les termes suivants :Pacte de carrière les mesures que le ministre présente devraient être la priorité de tout responsable de l'Éducation Nationale qui se soucie de ses personnels. Ceci afin de pousser les fédérations de fonctionnaires à s'engager plus avant dans la négociation pour appliquer la loi mobilité.L'industrie continue de s'affaisser en France source de nouvelles vagues de licenciements, pendant le vacarme des retraites. Journées d'action à répétition, émiettement des résistance pour endiguer la vague qui continue de monter contre Sarkozy ; la dernière manifestation à Paris fut menée par les chefs syndicaux & agrave; . l'église St Augustin le 28/10/10 évitant à tout prix de marcher sur l'Assemblée Nationale.L'onde de choc du vote de la loi du 10/08/2010 (contre le licenciement de 140.000 fonctionnaires aux Etats Unis, voir le récapitulatif p1777 http://www.box.net/shared/rr7x4aood6) n'en finit pas de se répercuter : pour la première fois depuis 1938, l'exécutif américain est neutralisé notamment dans sa poursuite des 8 millions de licenciements.Et la loi mobilité expé ;rimentée depuis 2003 au Maroc n'a pu conduire aux licenciements escomptés des fonctionnaires.Posologie pour la grippe saisonnière.bonne lecturepatry richarddans le cas où les liens ne s'ouvrent pas en cliqu ant dessus, les copier coller dans la barre d'adresse de votre navigateur.Parfois le lien s'ouvre difficilement, cliquez sur la flèche ronde à côté de la petite maison en haut à droite.version dochttps://docs.google.com/fileview?id=0Bwgoi13hj143ZTQ2ZTM4MTktMzQ1MC00Zjc1LWI3ODctZmJlNTAxZjNkM2Zm&hl=fr version pdf https://docs.google.com/fileview?id=0Bwgoi13hj143Zjg0ZWJlM2YtYjgzMS00ODRjLTk5YzgtNTA1YzQ3MWEwYTk3&hl=frou bien seulement les derniers fichiers sur :http://cid-2eb0d1438e827614.skydrive.live.com/redir.aspx?resid=2EB0D1438E827614!105&Bpub=SDX.Docs&Bsrc=GetSharingLinkSFR interrompt régulièrement l'envoi des courriels, dès lors émis en deux jours.Suite du fichier complet actualité mobilité 5/11/10 sur http://www.box.net/shared/rr7x4aood6Sur ce même site vous pouvez télécharger le résumé et le fichier actualité récapitulatif, 2.000 pages chronologiques regroupant tous les fichiers, et chercher par mot clef.Pour se désinscrire et tout contactpatry.rich...@wanadoo.fr133 av berger93290tremblay01/48/61/36/56___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginne
Re: [Caml-list] Causes for segfaults
On Thu, Nov 04, 2010 at 08:39:27PM +, Jamie Brandon wrote: > I'm not using Obj. I am unmarshalling. I have 'ulimit -s unlimited' [...] I once have used Marshall-Module, when exploring Ocaml the first time. I changed the saved marshalled files by hand and read them back, doing unmarshalling and this yielded a crash. Then I decided to never again use this module and also asked to remove such unsafe technics/modules from the standard lib, but as you can see, it was not removed. Should be an external add-on, or better, made safe. Ciao, Oliver ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
Re: [Caml-list] Causes for segfaults
> It might be intersting for you to run your app in gdb and sent the > backtrace of the segfault. Valgrind could also be very useful here but > it is not for the faint of heart. > > very quick guide to gdb (although I am sure you know): Not at all - spent my whole life in HLL land. Learning to use gdb is probably long overdue. > _ 1) Make sure your program is compiled with -g Ocaml 3.9 can't compile native code with -g :( Installing newer versions of ocaml on old installations of centOS is ... entertaining. Despite the delay, I did eventually get this to work. [r...@senldogo0183 texsearch-development2]# gdb ./index GNU gdb Red Hat Linux (6.5-25.el5rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"...(no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (gdb) run Starting program: /data/texsearch-development2/index (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496271328 (LWP 30551)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912496271328 (LWP 30551)] 0x004466e5 in camlIndex__run_query_1442 () (gdb) bt #0 0x004466e5 in camlIndex__run_query_1442 () #1 0x4e21 in ?? () #2 0x0056050c in caml_ml_close_channel () #3 0x0078d0a0 in camlIndex () #4 0x0001 in ?? () #5 0x7fff in ?? () #6 0x2ab04900 in ?? () #7 0x00447e98 in camlIndex__entry () #8 0x2ab04900 in ?? () #9 0x0078d890 in camlIndex__142 () #10 0x0078d808 in camlIndex__140 () #11 0x0078d928 in camlIndex__144 () #12 0x0078d8c0 in camlIndex__143 () #13 0x2ab03a58 in ?? () #14 0x0078d7c0 in camlIndex__123 () #15 0x0078d828 in camlIndex__141 () #16 0x0078dab0 in camlIndex__146 () #17 0x2ab03918 in ?? () #18 0x0078d7e8 in camlIndex__139 () #19 0x2ab038e8 in ?? () #20 0x0078da78 in camlIndex__145 () #21 0x2ab038c0 in ?? () #22 0x2ab03a40 in ?? () #23 0x2ab03a28 in ?? () #24 0x2ab03a10 in ?? () #25 0x2ab039f8 in ?? () #26 0x2ab039b0 in ?? () #27 0x2ab03960 in ?? () #28 0x0201 in ?? () #29 0x0043fdc9 in caml_startup__code_begin () #30 0x002c5123 in ?? () #31 0x0056996e in caml_start_program () I'm not sure how to interpret this. run_query doesnt *directly* do anything but it calls into other modules (suffix_array etc) that are in the same directory. It looks to me like I screwed up the build process and there are no debugging symbols for suffix_array and co. This is what I did: ocamlfind ocamlopt -linkpkg -g \ -package extlib \ -package netclient \ -package json-wheel \ -package json-static \ -package xml-light \ -package str \ -syntax camlp4o \ -package json-static \ util.mli util.ml \ pid.mli pid.ml \ latex.mli latex.ml \ edit.ml \ suffix_array.mli suffix_array.ml \ query.ml \ index.ml \ -o index Any ideas? ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
Re: [Caml-list] Causes for segfaults
Hi, On Sat, Nov 06, 2010 at 12:14:31AM +0100, Jamie Brandon wrote: I had a Segmentation Fault some days ago in native code. Compiling with bytecode, it raised Stack_overflow. The bug was that I called a non tail-recursive function. Is your stack size unlimited ? (command: ulimit -a) If it is, perhaps try to limit it and try again in bytecode to see if the Segmentation Fault is transformed into a Stack Overflow. -- Daniel de Rauglaudre http://pauillac.inria.fr/~ddr/ ___ Caml-list mailing list. Subscription management: http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list Archives: http://caml.inria.fr Beginner's list: http://groups.yahoo.com/group/ocaml_beginners Bug reports: http://caml.inria.fr/bin/caml-bugs
