M-Labs/nac3
M-Labs
/
nac3
8
0
Fork 10
Code Issues 98 Pull Requests 20 Releases Wiki Activity

nac3 segfault with phaser driver #240

New Issue
Closed
opened 2022-03-26 16:02:18 +08:00 by sb10q · 4 comments
sb10q commented 2022-03-26 16:02:18 +08:00
Owner
Copy Link

Uncomment these two lines:
317c257778

> artiq_compile nac3devices.py
fish: Job 1, 'artiq_compile nac3devices.py' terminated by signal SIGSEGV (Address boundary error)
Uncomment these two lines: https://github.com/m-labs/artiq/commit/317c257778edbbda1b0d87426379368e0126de0b ``` > artiq_compile nac3devices.py fish: Job 1, 'artiq_compile nac3devices.py' terminated by signal SIGSEGV (Address boundary error) ```
sb10q added this to the Prealpha milestone 2022-03-26 16:02:18 +08:00
sb10q added the
high-priority
 label 2022-03-26 16:02:18 +08:00
pca006132 was assigned by sb10q 2022-03-26 17:35:20 +08:00
pca006132 commented 2022-03-26 18:43:46 +08:00
Contributor
Copy Link

I guess this kind of issue is related to #241

I guess this kind of issue is related to #241
ychenfo commented 2022-03-26 18:49:41 +08:00
Collaborator
Copy Link

I guess this kind of issue is related to #241

Might also be just about the recursive host type? IIRC previously the phaser driver segfault is fixed by handling the recursive host object

> I guess this kind of issue is related to #241 Might also be just about the recursive host type? IIRC previously the phaser driver segfault is fixed by handling the recursive host object
pca006132 commented 2022-03-26 19:28:51 +08:00
Contributor
Copy Link

I guess this kind of issue is related to #241

Might also be just about the recursive host type? IIRC previously the phaser driver segfault is fixed by handling the recursive host object

Yes. And is not related to #421.

> > I guess this kind of issue is related to #241 > > Might also be just about the recursive host type? IIRC previously the phaser driver segfault is fixed by handling the recursive host object Yes. And is not related to #421.
sb10q commented 2022-03-26 20:20:23 +08:00
Author
Owner
Copy Link

Works now, thanks for fixing this quickly.

Works now, thanks for fixing this quickly.
sb10q closed this issue 2022-03-26 20:20:23 +08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
ndstrides-neo-next
misc/impl-tracert
ndstrides-14-end
ndstrides-13-tests
ndstrides-12-builtins
ndstrides-11-matmul
ndstrides-10-ops
ndstrides-9-subassign
ndstrides-8-transpose
ndstrides-7-broadcasting
ndstrides-6-reshape
ndstrides-5-miscfuncs
ndstrides-4-nparray
ndstrides-3-indexing
ndstrides-2-basic
ndstrides-1-model
ndstrides
refactor_composer
misc/update-pyo3
misc/mold
ndstrides-1-model-lifetime
ndstrides-enhance-irrt
ndstrides-intro
issue-313
refactor-primstore
numpy-anyall
enhance/cargo-test-standalone-demos
issue-136
rpc-obj-as-param
iterators
escape-analysis
refactor_anto
Labels
Clear labels   
future-extension

   
high-priority

   
low-priority

   
UROP0622
No Label
future-extension
high-priority
low-priority
UROP0622
Milestone
Clear milestone
No items
No Milestone
Prealpha
Assignees
Clear assignees
No Assignees
pca006132
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/nac3#240
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?