hugin-devs team mailing list archive

[hvdwolf <1011111@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This is already a long standing issue since the very first versions of cpfind. As cpfind is not really neccessary as 64bit as it will (almost) never reach the 4GB file/memory boundary when creating control points I did not file a bug earlier.
cpfind always ends  in a segmeantation fault when run on a project, no matter the number or size of the images.
When running "cpfind --help" it simply works so it's really in the image analyzing.

The simple "error log" is from the terminal is:
./cpfind -o pipo.pto ~/Pictures/panorama/1222-021-1222-025.pto 
ThreadQueue created
Hugin's cpfind 2011.5.0.5833:db2f378e1c08 built by Harry van der Wolf
based on Pan-o-matic by Anael Orlinski

The available memory does not allow running 2 threads parallel.
Running cpfind with 1 threads.
User thread created.
Reference thread created.
1 reference-thread added.
pollPendingThreads()
1 user-thread added.
Thread starting...

Project contains the following images:
Image 0
  Imagefile: 1222-021.JPG
  Remapped : no
Image 1
  Imagefile: 1222-022.JPG
  Remapped : no
Image 2
  Imagefile: 1222-023.JPG
  Remapped : no
Image 3
  Imagefile: 1222-024.JPG
  Remapped : no
Image 4
  Imagefile: 1222-025.JPG
  Remapped : no

--- Analyze Images ---
i0 : Analyzing image...
i1 : Analyzing image...
i2 : Analyzing image...
i3 : Analyzing image...
Segmentation fault

The only line added to the system log is:
Jun 10 11:30:23 Antares-6 ReportCrash[54303]: Saved crash report for cpfind[54300] version ??? (???) to /Users/harryvanderwolf/Library/Logs/DiagnosticReports/cpfind_2012-06-10-113023_Antares-6.crash


Please find attached a crash log.

** Affects: hugin
     Importance: Undecided
         Status: New


** Tags: 64bit cpfind fault segmentation

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1011111

Title:
  OSX 64bit cpfind always segfaults

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  This is already a long standing issue since the very first versions of cpfind. As cpfind is not really neccessary as 64bit as it will (almost) never reach the 4GB file/memory boundary when creating control points I did not file a bug earlier.
  cpfind always ends  in a segmeantation fault when run on a project, no matter the number or size of the images.
  When running "cpfind --help" it simply works so it's really in the image analyzing.

  The simple "error log" is from the terminal is:
  ./cpfind -o pipo.pto ~/Pictures/panorama/1222-021-1222-025.pto 
  ThreadQueue created
  Hugin's cpfind 2011.5.0.5833:db2f378e1c08 built by Harry van der Wolf
  based on Pan-o-matic by Anael Orlinski

  The available memory does not allow running 2 threads parallel.
  Running cpfind with 1 threads.
  User thread created.
  Reference thread created.
  1 reference-thread added.
  pollPendingThreads()
  1 user-thread added.
  Thread starting...

  Project contains the following images:
  Image 0
    Imagefile: 1222-021.JPG
    Remapped : no
  Image 1
    Imagefile: 1222-022.JPG
    Remapped : no
  Image 2
    Imagefile: 1222-023.JPG
    Remapped : no
  Image 3
    Imagefile: 1222-024.JPG
    Remapped : no
  Image 4
    Imagefile: 1222-025.JPG
    Remapped : no

  --- Analyze Images ---
  i0 : Analyzing image...
  i1 : Analyzing image...
  i2 : Analyzing image...
  i3 : Analyzing image...
  Segmentation fault

  The only line added to the system log is:
  Jun 10 11:30:23 Antares-6 ReportCrash[54303]: Saved crash report for cpfind[54300] version ??? (???) to /Users/harryvanderwolf/Library/Logs/DiagnosticReports/cpfind_2012-06-10-113023_Antares-6.crash

  
  Please find attached a crash log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1011111/+subscriptions