Recherche avancée

Sur d’autres sites (5001)

• Error inclunding in FFMPEG project on a Mac using clang

  3 juillet 2018, par benwiz

  I’m having trouble running the remuxing.c example code. I get the following error. I have confirmed that the files can be found in /usr/local/include. I am running macOS Sierra 10.12.6.

  $ cc -v playground/remuxing.c
  
  Apple LLVM version 9.0.0 (clang-900.0.39.2)
  
  Target: x86_64-apple-darwin16.7.0
  
  Thread model: posix
  
  InstalledDir: /Library/Developer/CommandLineTools/usr/bin
  
   "/Library/Developer/CommandLineTools/usr/bin/clang" -cc1 -triple x86_64-apple-macosx10.12.0 -Wdeprecat
  
  ed-objc-isa-usage -Werror=deprecated-objc-isa-usage -emit-obj -mrelax-all -disable-free -disable-llvm-v
  
  erifier -discard-value-names -main-file-name remuxing.c -mrelocation-model pic -pic-level 2 -mthread-mo
  
  del posix -mdisable-fp-elim -fno-strict-return -masm-verbose -munwind-tables -target-cpu penryn -target
  
  -linker-version 305 -v -dwarf-column-info -debugger-tuning=lldb -resource-dir /Library/Developer/Comman
  
  dLineTools/usr/lib/clang/9.0.0 -fdebug-compilation-dir /Users/myuser/github/personal/synthesthesi
  
  a -ferror-limit 19 -fmessage-length 103 -stack-protector 1 -fblocks -fobjc-runtime=macosx-10.12.0 -fenc
  
  ode-extended-block-signature -fmax-type-align=16 -fdiagnostics-show-option -fcolor-diagnostics -o /var/
  
  folders/8s/2xc3v8dd7zz2c2trymzybvd534bnhg/T/remuxing-819223.o -x c playground/remuxing.c
  
  clang -cc1 version 9.0.0 (clang-900.0.39.2) default target x86_64-apple-darwin16.7.0
  
  #include "..." search starts here:
  
  #include <...> search starts here:
  
   /usr/local/include
  
   /Library/Developer/CommandLineTools/usr/lib/clang/9.0.0/include
  
   /Library/Developer/CommandLineTools/usr/include
  
   /usr/include
  
   /System/Library/Frameworks (framework directory)
  
   /Library/Frameworks (framework directory)
  
  End of search list.
  
   "/Library/Developer/CommandLineTools/usr/bin/ld" -demangle -lto_library /Library/Developer/CommandLineTools/usr/lib/libLTO.dylib -no_deduplicate -dynamic -arch x86_64 -macosx_version_min 10.12.0 -o a.out /var/folders/8s/2xc3v8dd7zz2c2trymzybvd534bnhg/T/remuxing-819223.o -lSystem /Library/Developer/CommandLineTools/usr/lib/clang/9.0.0/lib/darwin/libclang_rt.osx.a
  
  Undefined symbols for architecture x86_64:
  
    "_av_dump_format", referenced from:
  
        _main in remuxing-819223.o
  
    "_av_freep", referenced from:
  
        _main in remuxing-819223.o
  
    "_av_interleaved_write_frame", referenced from:
  
        _main in remuxing-819223.o
  
    "_av_mallocz_array", referenced from:
  
        _main in remuxing-819223.o
  
    "_av_packet_unref", referenced from:
  
        _main in remuxing-819223.o
  
    "_av_read_frame", referenced from:
  
        _main in remuxing-819223.o
  
    "_av_rescale_q", referenced from:
  
        _main in remuxing-819223.o
  
    "_av_rescale_q_rnd", referenced from:
  
        _main in remuxing-819223.o
  
    "_av_strerror", referenced from:
  
        _av_make_error_string in remuxing-819223.o
  
    "_av_write_trailer", referenced from:
  
        _main in remuxing-819223.o
  
    "_avcodec_parameters_copy", referenced from:
  
        _main in remuxing-819223.o
  
    "_avformat_alloc_output_context2", referenced from:
  
        _main in remuxing-819223.o
  
    "_avformat_close_input", referenced from:
  
        _main in remuxing-819223.o
  
    "_avformat_find_stream_info", referenced from:
  
        _main in remuxing-819223.o
  
    "_avformat_free_context", referenced from:
  
        _main in remuxing-819223.o
  
    "_avformat_new_stream", referenced from:
  
        _main in remuxing-819223.o
  
    "_avformat_open_input", referenced from:
  
        _main in remuxing-819223.o
  
    "_avformat_write_header", referenced from:
  
        _main in remuxing-819223.o
  
    "_avio_closep", referenced from:
  
        _main in remuxing-819223.o
  
    "_avio_open", referenced from:
  
        _main in remuxing-819223.o
  
  ld: symbol(s) not found for architecture x86_64
  
  clang: error: linker command failed with exit code 1 (use -v to see invocation)

• It’s January 28th : Let’s celebrate Data Privacy !

  29 janvier 2018, par Matomo Core Team

  It is a special Sunday here for us at Matomo, as today is international Data Privacy Day. The day was created in 2007 to raise awareness of the importance of data privacy for people and businesses worldwide.

  

  What is data privacy about ?

  Personal data refers to any data which is collected and can be linked to an individual human being such as phone records, credit card transactions, GPS position, IP addresses, browsing history… So basically, personal data refers to your identity online. That is why you should be highly concerned about sending your personal data (or your customers’ personal data) away. It is important to be aware of who is collecting the information and how it is being used.

  What big changes are happening in 2018 ?

  New privacy regulations GDPR comes into play next May 2018 : GDPR will bring about some changes (in the right direction) by making people and businesses aware of what data privacy means, and what they should be doing to protect their customers’ privacy. With these new regulations, data privacy awareness is reaching a critical milestone this year.

  How can I protect my privacy ?

  Here are a few tips to protect your privacy :

  • Educate yourself on the importance of privacy : the more informed you are the better.
  • Use open source solutions where you can keep full control of your own data (such as NextCloud instead of Dropbox and of course Matomo instead of Google Analytics),
  • Experiment with different online services to protect your data privacy, for example using an alternative search engine (such as DuckDuckGo instead of Google) or an alternative email provider (such as ProtonMail).

  What’s coming next for Matomo and Privacy ?

  Here at Matomo, we are building the leading decentralised open web analytics platform. We’re currently working on new sets of privacy features to make compliance with GDPR a breeze. Stay tuned here to be notified when we launch the new privacy compliance tools !

  And in case you’ve missed this important info, you may be interested in :

  • Configure Privacy Settings in Matomo
  • 11 ways Matomo Analytics helps you to protect your visitors privacy

   

  The post It’s January 28th : Let’s celebrate Data Privacy ! appeared first on Analytics Platform - Matomo.

• Android ffmpeg release :invalid address or address of corrupt block passed to dlfree

  11 janvier 2018, par jcguo

  guys.I’m new to Android JNI development as well as ffmpeg libs.

  With some struggles, I have managed to decode the real time H264 data, but meeting error when release the ffmpeg decoder :

  12-11 19:54:36.428  27959-27959/com.example.firmament.dji A/libc﹕ invalid address or address of corrupt block 0x6fa13868 passed to dlfree
  
  12-11 19:54:36.430  27959-27959/com.example.firmament.dji A/libc﹕ Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 27959 (e.firmament.dji)

  Some questions in stackoverflow mentioned that this error related to wrongly free some memory which was protected(same with Segment Fault).

  I checked the C JNI code for times and could not fix the bug, here is my code(release part) :

  jint Java_com_example_firmament_dji_XKZH264_release(JNIEnv *env, jobject obj)
  
  {
  
      if (pFrame != NULL) {
  
          av_free(pFrame);
  
          pFrame = NULL;
  
      }
  
  
  
      if (pCodecContext != NULL) {
  
          avcodec_close(pCodecContext);
  
          av_free(pCodecContext);
  
          pCodecContext = NULL;
  
      }
  
  
  
      if (pParserContext != NULL) {
  
          av_parser_close(pParserContext);
  
          av_free(pParserContext);
  
          pParserContext = NULL;
  
      }
  
  
  
      DeleteYUVTab();
  
  
  
      return 1;
  
  }
  
  
  
  void DeleteYUVTab()
  
  {
  
      if (colortab != NULL) {
  
          av_free(colortab);
  
          colortab = NULL;
  
      }
  
  
  
      if (rgb_2_pix != NULL) {
  
          av_free(rgb_2_pix);
  
          colortab = NULL;
  
      }
  
  }