runtime: goroutine stack exceeds 1000000000-byte limit

Bug #2024386 reported by Sergio Cazzolato
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Image
Fix Committed
Undecided
Unassigned

Bug Description

In snapd we build ubuntu-image with test keys like this:

go get github.com/canonical/ubuntu-image/cmd/ubuntu-image
go install -tags 'withtestkeys' github.com/canonical/ubuntu-image/cmd/ubuntu-image

Then when we try to build and ubuntu core image we get the following error

/home/gopath/bin/ubuntu-image snap -w /home/image /home/image/pc.model --channel edge --snap /home/image/pc-kernel_5.4.0-152.169.1_amd64.snap --snap /home/image/pc-repacked.snap --snap /home/image/core20.snap --snap /home/image/snapd_2.59.5+git966.gcc7fab5_amd64.snap --output-dir /home/image
[0] make_temporary_directories
[1] determine_output_directory
[2] prepare_image
WARNING: proceeding to download snaps ignoring validations, this default will change in the future. For now use --validation=enforce for validations to be taken into account, pass instead --validation=ignore to preserve current behavior going forward
WARNING: "snapd", "pc-kernel", "pc" installed from local snaps disconnected from a store cannot be refreshed subsequently!
[3] load_gadget_yaml
[4] set_artifact_names
[5] populate_rootfs_contents
[6] generate_disk_info
[7] calculate_rootfs_size
[8] populate_bootfs_contents
[9] populate_prepare_partitions
[10] make_disk
[11] generate_manifest
[12] finish
runtime: goroutine stack exceeds 1000000000-byte limit
runtime: sp=0xc0204643b0 stack=[0xc020464000, 0xc040464000]
fatal error: stack overflow

runtime stack:
runtime.throw({0xe9c13a?, 0x15695e0?})
 /snap/go/current/src/runtime/panic.go:1047 +0x5d fp=0x7f6bc9de3cc0 sp=0x7f6bc9de3c90 pc=0x436e1d
runtime.newstack()
 /snap/go/current/src/runtime/stack.go:1105 +0x5bd fp=0x7f6bc9de3e70 sp=0x7f6bc9de3cc0 pc=0x450c9d
runtime.morestack()
 /snap/go/current/src/runtime/asm_amd64.s:574 +0x8b fp=0x7f6bc9de3e78 sp=0x7f6bc9de3e70 pc=0x46794b

Revision history for this message
Łukasz Zemczak (sil2100) wrote :

I think this should be fixed now, right?

Changed in ubuntu-image:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.