Recherche avancée

Sur d’autres sites (10913)

• Of ctors and dtors

  18 février 2011, par Multimedia Mike — Programming, Sega Dreamcast

  I haven’t given up on the Sega Dreamcast programming. I was able to compile a bunch of homebrew code for the DC many years ago and I can’t make it work anymore. Again, I was working with a purpose-built, open source RTOS named KallistiOS (or KOS). I can make the programs compile but not run. I had ELF files left over from years ago which still executed. But when I tried to build new ELF files, no luck— the programs crashed before even reaching my main() function.

  I found the problem : ELF files are comprised of a number of sections and 2 of these sections are named ’.ctors’ and ’.dtors’ which stand for constructors and destructors. The KOS RTOS performs a manual traversal of .ctors section during program initialization and this is where things go bad. The traversal code doesn’t seem to account for a .ctors section that only contains a single entry. I commented out the function that does the traversal and programs started to work, at least until it was time to exit the program and return control to the program loader. That’s when the counterpart .dtors section traversal code ran and demonstrated the same problem. I’ll exhibit the problematic code at the end of this post.

  So I’m finally tinkering with Sega Dreamcast programming once again and with a slightly better grasp of software engineering than the first time I did this.

  Portable and Compatible C ?
  If nothing else, this low-level embedded stuff exposes you to some serious toolchain arcana, the likes of which you will likely never see working strictly in the desktop arena.

  Still, this exercise makes me wonder why C code from a decade ago doesn’t compile reliably now. Part of it is because gcc has gotten stricter about the syntax it will accept. In the case of this specific crashing problem, I suspect it comes down to a difference in the way the linker generates the final ELF file. I’ve written a list of items I have had to modify in the KOS codebase in order to get it to compile on more recent gcc versions. I wonder if it would be worth publishing the specifics, or if anyone would ever find the information useful ? Oh, who am I kidding ? Of course I’ll write it up, perhaps publish a new version of the code, if only because that’s the best chance I have of finding my own work again some years down the road.

  Problematic C Code
  See if this code makes any sense to you. It somehow traverse a list of 32-bit function pointers (in different directions, depending on constructors or destructors), executing each in turn. However, it appears to fall over if the list of pointers consists of a single entry.
  

  PLAIN TEXT

  C :

  1. typedef void (*fptr)(void) ;
  2.  
  3. static fptr ctor_list[1] __attribute__((section(".ctors"))) = { (fptr) -1 } ;
  4. static fptr dtor_list[1] __attribute__((section(".dtors"))) = { (fptr) -1 } ;
  5.  
  6. /* Call this to execute all ctors */
  7. void arch_ctors() {
  8.     fptr *fpp ;
  9.  
  10.     /* Run up to the end of the list (defined by crtend) */
  11.     for (fpp=ctor_list + 1 ; *fpp != 0 ; ++fpp)
  12.          ;
  13.  
  14.     /* Now run the ctors backwards */
  15.     while (—fpp> ctor_list)
  16.         (**fpp)() ;
  17. }
  18.  
  19. /* Call this to execute all dtors */
  20. void arch_dtors() {
  21.     fptr *fpp ;
  22.  
  23.     /* Do the dtors forwards */
  24.     for (fpp=dtor_list + 1 ; *fpp != 0 ; ++fpp )
  25.         (**fpp)() ;
  26. }

• Evolution #3089 : Suppression des rubriques : informer des liens qui empêchent

  11 août 2014, par Fil Up

  un message de neofutur qui dit quelque chose de similaire :

  ```
  09:41 (02:58) < neofutur>
  http://forum.spip.net/fr_256464.html#forum258451
  09:41 (02:58) < neofutur> a priori des tas de gens ont ce probleme
  09:41 (03:00) < neofutur> empecher la suppression de la sous
  rubrique vide parce qu elle a une photo associee en tant que
  logo . . . ca meriterai une explication
  09:41 (05:04) < neofutur> peut etre avoir un bouton "supprimer" qyi
  est inactif ( greyed ) avec un survol qui dit "supprimer d
  abord le logo . . ."
  ```

• Evolution #2999 (Nouveau) : Pourvoir personnaliser le contenu de la constante _IS_BOT

  13 mai 2013, par - Equipement

  Bonjour,

  Les signatures des moteurs d’indexations sont définies dans ecrire/inc_version.php, AVANT le chargement du fichier mes_options.php (et avant le chargement des plugins).

  Aussi, je ne vois pas comment on peut compléter cette liste de signatures via le fichier mes_options.php où via un plugin.

  Lorsqu’on utilise mnogosearch sur des sites intranets, ce serait commode.
  Par ailleurs, d’autres ont eu également ce besoin : http://forum.spip.net/fr_247990.html

  Cordialement
  Equipement