Recherche avancée

Sur d’autres sites (12160)

• Why does linking different MSVC Run-Time Libraries crash in release mode ?

  9 septembre 2014, par UmNyobe

  I am using ffmpeg and Qt to build a small demo app.

  • FFmpeg is built with /MT (crossbuild or built with visual 2010)
  • Qt is always built with /MD
  • My little example is always built with /MD

  When the application

  int main(int argc, char *argv[])
  
  {
  
      QApplication a(argc, argv);
  
  
  
      av_gcd (75, 25);
  
  
  
      return a.exec();
  
  }
  
  
  
  //note : following is av_gcd source in ffmpeg libs:
  
  int64_t av_gcd(int64_t a, int64_t b)
  
  {
  
      if (b)
  
          return av_gcd(b, a % b);
  
      else
  
          return a;
  
  }

  is executed in release mode it crashes because it doesn’t see av_gcd as executable memory. The error is :

  First-chance exception at 0x0000000300905a4d in mylittleexample.exe :
  0xC0000005 : Access violation at location 0x0000000300905a4d.

  =======================================
  VERIFIER STOP 0000000000000650 : pid 0x1B9C : Attempt to execute code in
  non-executable memory (first chance).

  0000000300905A4D : Address being accessed.
  0000000300905A4D : Code
  performing invalid access.
  00000000009FF770 : Exception record. Use
  .exr to display it.
  00000000009FF280 : Context record. Use .cxr to
  display it.

  =======================================

  The address 0x0000000300905a4d doesnt change regardless of the function in the library (ffmpeg in this case), or the compiler used for the executable (vs2010, vs2012) or a different machine.

  If I use the FFmpeg built with /MD and it works as one would expect.

  1. I observe that the executable doesnt load the library when the
     library is compiled with /MT. Why is that ?
  2. Furthermore, If the library is compiled with /MT and debug
     information is enabled when the application is linked (/DEBUG
     param to the linker) then the library is loaded and everything
     execute correctly. Why ?

• End of Piwik Mobile 1 – Focus is on Piwik Mobile 2

  2 septembre 2014, par Piwik Core Team — Community, Piwik Mobile Releases

  More than four years after its initial release, we will remove Piwik Mobile 1 from the Apple App Store and Google Play Store in one week. During that time the app was downloaded more than 60.000 times with an average rating of 4.6 and over 2000 ratings. Thank you to our community of users for all of this !

  Why we must focus on Piwik Mobile 2

  Unfortunately we do not have the resources to maintain Piwik Mobile 1 to be compatible with the latest iOS and Android updates (namely iOS 8 and Android L). The last update of Piwik Mobile 1 was over one year ago and the underlying framework, which we are using to develop the app, is nearly two years old. Making the code compatible with the current version of the underlying framework to support the latest platform versions would take us many weeks. As a little background : From the beginning Piwik Mobile 1 has been a free app and was developed by a single person Thomas in his spare time who is now focussing on Piwik Mobile 2.

  Can I still get it ?

  We are announcing this today so you get a chance to install the app via the Apple App Store and Google Play Store while it is still available.

  If you are one of the 87% of our Piwik Mobile 1 users who are already using Android 4+ or iOS 7+ then you can install Piwik Mobile 2 (make sure you upgrade your Piwik platform to 1.12 or 2.x recommended).

  What happens after the app is removed ?

  If you have already installed the app it won’t be removed from your device and you will still be able to use it. Android users can still download Piwik Mobile 1 but we cannot guarantee it will work on all devices. Lastly the code our free software is available on GitHub and you can build it from the source if you have to.

  The future of Piwik Mobile

  Piwik Mobile version 2.1 is currently in beta testing phase. This new version includes several useful new features such as support for Segmentation. If you use Android, give it a try !

• Anomalie #3298 (Nouveau) : Erreur 404 retournée lors de l’accès à l’URL arborescente générée pour ...

  16 octobre 2014, par Guillaume Fahrner

  Tout est dans le titre :)

  Un auteur dont le nom commence par 0x va avoir une URL arbo générée non valide :

  Un auteur dont le nom est 0xA47 va créer cette entrée dans la table spip_urls :
  

  mysql> select * from spip_urls where date=’0000-00-00 00:00:00’ and type=’auteur’ ;
  +-------+--------+----------+---------------------+-----------+----------+-------+
  
  
  
  url
  type
  id_objet
  date
  id_parent
  segments
  perma
  
  
  +-------+--------+----------+---------------------+-----------+----------+-------+
  
  
  
  0xA47
  auteur
  15838
  0000-00-00 00:00:00
  0
  1
  0
  
  
  +-------+--------+----------+---------------------+-----------+----------+-------+
  
  1 row in set (0.02 sec)
  

  La valeur de la date pose problème je pense (0000-00-00 00:00:00).

  L’URL généré par /ecrire/ ?exec=auteur&action=redirect&type=auteur&id=15838&var_mode=preview me redirige sur /0xA47 ?var_mode=preview qui abouti sur une erreur HTTP 404.

  De manière assez aléatoire j’ai une seconde URL générée dans la table spip_urls de la forme : 0xA47-[identifiant] qui elle est valide (elle n’a pas le champ date à 0).