*/}}

#5 Buffer overflow when export/save.

Open
opened 1 year ago by levprotter · 3 comments

"Prop not recorded as DBInst. Prop not recorded as DBInst. *** buffer overflow detected ***: terminated fish: “./OurPaint-v0.1-x86_64.AppImage” terminated by signal SIGABRT (Abort) " in bash "b 0 0 b 1 0 b 2 0 b 3 0 b 4 0 a 0 0 a 1 0 *** buffer overflow detected ***: terminated Aborted (core dumped) "

"Prop not recorded as DBInst. Prop not recorded as DBInst. *** buffer overflow detected ***: terminated fish: “./OurPaint-v0.1-x86_64.AppImage” terminated by signal SIGABRT (Abort) " in bash "b 0 0 b 1 0 b 2 0 b 3 0 b 4 0 a 0 0 a 1 0 *** buffer overflow detected ***: terminated Aborted (core dumped) "
chengdulittlea commented 1 year ago
Owner

Hello! Would you please include a reproduce step? Tell me approximately what you did on the canvas (or how it's drawn roughly/provide a screenshot before saving) and I'll see what's wrong.

Is it crashing for both exporting and saving? or it's just exporting?

There's a potential bug that I already fixed for exporting and will be available shortly in the next version.

Hello! Would you please include a reproduce step? Tell me approximately what you did on the canvas (or how it's drawn roughly/provide a screenshot before saving) and I'll see what's wrong. Is it crashing for both exporting and saving? or it's just exporting? There's a potential bug that I already fixed for exporting and will be available shortly in the next version.
levprotter commented 1 year ago
Poster

Even with zero modification, attempting to do any read/write to a file does it. Is there a more verbose debug mode or something? I can go ahead and compile from source at some point, but am a bit busy atm.

Even with zero modification, attempting to do any read/write to a file does it. Is there a more verbose debug mode or something? I can go ahead and compile from source at some point, but am a bit busy atm.
chengdulittlea commented 1 year ago
Owner

No there's no verbose debug mode yet. That sounds pretty weird if reading doesn't work either. But if you can compile, hopefully there would be a stack trace available...

Are you on v0.1 or v0.1a (just updated today)? v0.1a might be working.

No there's no verbose debug mode yet. That sounds pretty weird if reading doesn't work either. But if you can compile, hopefully there would be a stack trace available... Are you on v0.1 or v0.1a (just updated today)? v0.1a might be working.
Sign in to join this conversation.
No Label
No Milestone
No assignee
2 Participants
Loading...
Cancel
Save
There is no content yet.