Please rebuild saga against latest gdal

[Johan Van de Wauw]

Saga is currently unusable as it tries to use an old version of gdal (which was updated for vivid). Rebuilding saga fixes the issue.

Without rebuilding the package can not be used, so this is a severe issue.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: saga 2.1.2+dfsg-3
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic i686
ApportVersion: 2.16.2-0ubuntu3
Architecture: i386
CurrentDesktop: Unity
Date: Tue Mar 17 18:18:10 2015
ExecutablePath: /usr/bin/saga_cmd
InstallationDate: Installed on 2015-01-31 (45 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150128)
ProcCmdline: saga_cmd
SegvAnalysis:
 Segfault happened at: 0xb710fca6 <__strlen_sse2_bsf+22>: movdqu (%edi),%xmm1
 PC (0xb710fca6) ok
 source "(%edi)" (0x5f444d44) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: saga
StacktraceTop:
 CPLStrdup () from /usr/lib/libgdal.so.1
 CSLDuplicate () from /usr/lib/libgdal.so.1
 GDALMultiDomainMetadata::SetMetadata(char**, char const*) () from /usr/lib/libgdal.so.1
 GDALMajorObject::SetMetadata(char**, char const*) () from /usr/lib/libgdal.so.1
 ?? () from /usr/lib/libgdal.so.1
Title: saga_cmd crashed with SIGSEGV in CPLStrdup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 CPLStrdup (pszString=0x5f444d44 <error: Cannot access memory at address 0x5f444d44>) at cpl_conv.cpp:252
 CSLDuplicate (papszStrList=0xb4bb64ea) at cpl_string.cpp:220
 GDALMultiDomainMetadata::SetMetadata (this=0x863c2fc, papszMetadata=0xb4bb64ea, pszDomain=0xb4bb6596 "") at gdalmultidomainmetadata.cpp:126
 GDALMajorObject::SetMetadata (this=0x863c2f0, papszMetadataIn=0xb4bb64ea, pszDomain=0xb4bb6596 "") at gdalmajorobject.cpp:291
 VRTDriver::SetMetadata (this=0x863c2f0, papszMetadata=0xb4bb64ea, pszDomain=0xb4bb6596 "") at vrtdriver.cpp:104

[Launchpad Janitor (janitor)]

This bug was fixed in the package saga - 2.1.4+dfsg-1ubuntu1

---------------
saga (2.1.4+dfsg-1ubuntu1) vivid; urgency=medium

  * 0099-no-hdf5.patch: Disable hdf5 to match libvigraimpex (LP: #1423670)
  * Rebuild against the latest ABI version of libgdal-dev (LP: #1433255)
 -- Adam Conrad <email address hidden> Wed, 18 Mar 2015 16:11:56 -0600

[Terry Sobecki (tsobecki4)]

I am running ubuntu 3.19.0-77-generic #85~14.04.1 LTR, and have SAGA version 2.2.7 installed from Synaptic Package Manager. I still seem to have this bug even though it was fixed in earlier versions of SAGA, as when I try to execute saga_cmd (command line for SAGA GIS) I get a segmentation fault and core dump:

saga_cmd crased with SIGSEGV in MLBB_Initialize()
Cannot access memeory at address 0x14b96
SegvAnalysis Segfault happended at : 0x14b96: Cannot accress memory at address 0x14b96
PC(0x00014b96) not located in a known VMA region (needed executable region)
SegvReason: executing unknown VMA
Signal: 11, etc

I had the Apport output sent in as an error report.
Any information about this "bug" or if it is indeed still a "bug" would be appreciated.
Thank you.

gdal version I'm using is 2.1.0, again installed via Synaptic Package Manager as part of the ubuntu-gis set of packages

[Terry Sobecki (tsobecki4)]

I just several minutes ago sent in a comment on a continued "bug" in this vein. After doing some checking and rerunning the saga_cmd executable I believe the error was on my part in inadvertently setting an environment variable which was no longer needed for the version of SAGA (2.2.7) I am runnng. Seems current versions no longer need this environment variable, SAGA_MLB, set and unsetting it seems to have corrected the problem. It does seem odd, however, that having it set would cause an abend and resultant core dump, seems like there would be a "nicer" way to deal with the issue. However, sorry for any inconvenience this may have caused, and please ignore my comment. Also, I didn't want to send in any official bug notification, if I did please remove and/or ignore it.

Thanks.

Terry Sobecki