Thread overview
dub segfault
Feb 11, 2018
Joe
Feb 11, 2018
Seb
Feb 11, 2018
Joe
February 11, 2018
I'm getting a segmentation fault when I run 'dub build' and I specify a dependency. Specifically, the dependency is 'derelict-pq' but it could be anything (I tried 'dpq2' and even 'mysql-native', just for kicks). The segfault occurs when it's supposedly searching for the dependency.  Here's the partial output of 'dub --vverbose build'

Collecting dependencies for select
  Version selection for dependency derelict-pq (derelict-pq) of select is missing.
  Missing dependency derelict-pq >=3.0.0-beta.3 <3.1.0-0 of select
Checking for missing dependencies.
Search for versions of derelict-pq (1 package suppliers)
Segmentation fault

The dub.json is trivial and works to properly build a program with 'libpq' directly.  And two months ago I had built the derelict-pq sample program and AFAIR everything went fine.

When this first happened last night, code.dlang.org was temporarily not accessible but that's been resolved now.  Before I report this as an issue, I thought I'd get some feedback.  I'm running dub 1.7.0-2, built on Jan  3 2018, on Debian buster.
February 11, 2018
On Sunday, 11 February 2018 at 00:31:28 UTC, Joe wrote:
> I'm getting a segmentation fault when I run 'dub build' and I specify a dependency. Specifically, the dependency is 'derelict-pq' but it could be anything (I tried 'dpq2' and even 'mysql-native', just for kicks). The segfault occurs when it's supposedly searching for the dependency.  Here's the partial output of 'dub --vverbose build'
>
> Collecting dependencies for select
>   Version selection for dependency derelict-pq (derelict-pq) of select is missing.
>   Missing dependency derelict-pq >=3.0.0-beta.3 <3.1.0-0 of select
> Checking for missing dependencies.
> Search for versions of derelict-pq (1 package suppliers)
> Segmentation fault
>
> The dub.json is trivial and works to properly build a program with 'libpq' directly.  And two months ago I had built the derelict-pq sample program and AFAIR everything went fine.
>
> When this first happened last night, code.dlang.org was temporarily not accessible but that's been resolved now.  Before I report this as an issue, I thought I'd get some feedback.  I'm running dub 1.7.0-2, built on Jan  3 2018, on Debian buster.

DUB should never, ever segfault.
Please report an issue to the dub issue tracker (https://github.com/dlang/dub/issues) with a minimal example to reproduce. Thanks!

> built on Jan  3 2018, on Debian buster.

Ideally you could verify whether this also happens with the official release.
The quick way to try this:

---
. $(curl https://dlang.org/install.sh | bash -s)
dub
---

See also: https://dlang.org/install.html
February 11, 2018
On Sunday, 11 February 2018 at 00:59:10 UTC, Seb wrote:
> Ideally you could verify whether this also happens with the official release.

Installing the official (ldc) release doesn't cause the problem, so presumably this is a problem with the Debian buster release.  However, I notice the official dub reports as version 1.6.0 built on 6 Jan, whereas the official ldc is 1.7.0 and the Debian dub is, as mentioned before, 1.7.0-2, and the Debian ldc2 says it's version 1.5.0, based on DMD 2.075.1, i.e., the version numbers are confusing to say the least.