Bug: Figure out why this crashes #172

Closed
opened 2024-04-16 07:26:00 +01:00 by deavmi · 8 comments
Owner

Problem

Input source:

image

Result (segmentation fault):

image

Diagnosis

It must be the call to finding the container.

## Problem Input source: ![image](/attachments/fcd3d166-6414-4ec8-8cc5-1906cff83d86) Result (segmentation fault): ![image](/attachments/118eec4b-5579-45e2-9538-222171519afb) ## Diagnosis It must be the call to finding the container.
deavmi added this to the Basics milestone 2024-04-16 07:26:00 +01:00
deavmi added the
needsfix
label 2024-04-16 07:26:00 +01:00
deavmi self-assigned this 2024-04-16 07:26:00 +01:00
deavmi added this to the Dependency tree, type-checking and codegen project 2024-04-16 07:26:01 +01:00
Author
Owner

I do urgently need to figure out what is wrong here.

I do urgently need to figure out what is wrong here.
deavmi added the due date 2024-04-30 2024-04-16 07:37:29 +01:00
deavmi started working 2024-04-24 12:49:14 +01:00
Author
Owner

I actually want to take a look at this and figure out why it is crashing. I have a feeling actually idk why. Leet's see.

I actually want to take a look at this and figure out why it is crashing. I have a feeling actually idk why. Leet's see.
Author
Owner

It seems to be any pointer deref assignment, thinks

It seems to be any pointer deref assignment, thinks
Author
Owner

It seems to be any pointer deref assignment, thinks

It looks like something is left on the code queue?

> It seems to be any pointer deref assignment, thinks It _looks_ like something is left on the code queue?
Author
Owner

It seems to be any pointer deref assignment, thinks

It looks like something is left on the code queue?

Nah, would not be me thinks. Seems parenting problem.

> > It seems to be any pointer deref assignment, thinks > > It _looks_ like something is left on the code queue? Nah, would not be me thinks. Seems parenting problem.
Author
Owner

It seems to be any pointer deref assignment, thinks

It looks like something is left on the code queue?

Nah, would not be me thinks. Seems parenting problem.

Ah, looks like PointerDeref stuff has no recursive painting/parenting applied to it, that explains it

> > > It seems to be any pointer deref assignment, thinks > > > > It _looks_ like something is left on the code queue? > > Nah, would not be me thinks. Seems parenting problem. Ah, looks like PointerDeref stuff has no recursive painting/parenting applied to it, that explains it
Author
Owner

It seems to be any pointer deref assignment, thinks

It looks like something is left on the code queue?

Nah, would not be me thinks. Seems parenting problem.

Ah, looks like PointerDeref stuff has no recursive painting/parenting applied to it, that explains it

Yep! Found it :)

> > > > It seems to be any pointer deref assignment, thinks > > > > > > It _looks_ like something is left on the code queue? > > > > Nah, would not be me thinks. Seems parenting problem. > > Ah, looks like PointerDeref stuff has no recursive painting/parenting applied to it, that explains it Yep! Found it :)
deavmi removed reference feature/comments 2024-04-24 13:29:47 +01:00
deavmi added reference vardec_varass_dependency 2024-04-24 13:29:48 +01:00
Author
Owner

Fix has been pushed

Fix has been pushed ✅
deavmi stopped working 2024-04-24 13:37:13 +01:00
47 minutes 59 seconds
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Total Time Spent: 47 minutes 59 seconds
deavmi
47 minutes 59 seconds
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

2024-04-30

Dependencies

No dependencies set.

Reference: tlang/tlang#172
No description provided.