https://bugs.kde.org/show_bug.cgi?id=389419
Jos van den Oever changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #20 from Jos van den Oever ---
I can reproduce this error in a VirtualBox with Arch and rustc 1.25.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #19 from illis+...@beyond8labs.com ---
Found why docker wasn't producing working binaries for me - I needed to clear
out the demo/rust/target directory before rebuilding in docker :/
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #18 from illis+...@beyond8labs.com ---
Ok. I managed to dial down the problem a bit more - you wont have to install a
VM to reproduce :)
Compiling with rustc 1.24.1 - crash.
Compiling with rustc 1.22.1 - works fine.
I haven't tried inbetwe
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #17 from illis+...@beyond8labs.com ---
(In reply to Jos van den Oever from comment #15)
> That is very disappointing. What would be the quickest way for me to
> replicate your setup in a VM?
I did test in an Antegros install -> same bug. Mig
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #16 from illis+...@beyond8labs.com ---
(In reply to Jos van den Oever from comment #15)
> That is very disappointing. What would be the quickest way for me to
> replicate your setup in a VM?
I did test in an Antegros install -> same bug. Mig
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #15 from Jos van den Oever ---
That is very disappointing. What would be the quickest way for me to replicate
your setup in a VM?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #14 from illis+...@beyond8labs.com ---
Created attachment 111390
--> https://bugs.kde.org/attachment.cgi?id=111390&action=edit
valgrind_log_testing_#D11232
(In reply to Jos van den Oever from comment #13)
> https://phabricator.kde.org/D112
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #13 from Jos van den Oever ---
https://phabricator.kde.org/D11232 should work as a fix for this bug.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #12 from Jos van den Oever ---
I've built on the patch by illis. This is work in progress because it still
crashes in tests.
https://phabricator.kde.org/D11232
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #11 from illis+...@beyond8labs.com ---
(In reply to Jos van den Oever from comment #10)
> @illis+kde the patch looks good. Please add it to master.
Have added a diff to phabricator, with a review tag. Pretty new to the
phabricator/kde submis
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #10 from Jos van den Oever ---
@illis+kde the patch looks good. Please add it to master.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #9 from Bruno Bigras ---
(In reply to illis+kde from comment #8)
> Created attachment 95 [details]
> Patch to fix issue running the demo on Arch Linux
>
> Following on from jlode90's remark; I made some tweaks to get the demo
> working
https://bugs.kde.org/show_bug.cgi?id=389419
illis+...@beyond8labs.com changed:
What|Removed |Added
CC||illis+...@beyond8labs.com
--- Commen
https://bugs.kde.org/show_bug.cgi?id=389419
jlod...@gmail.com changed:
What|Removed |Added
CC||jlod...@gmail.com
--- Comment #7 from jlod..
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #6 from Bruno Bigras ---
(In reply to Jos van den Oever from comment #5)
> Does the demo in demo/ work?
No I have a segmentation fault (see the end of my comment).
> I've tried to reproduce the problem but cannot. I've tried on my machine a
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #5 from Jos van den Oever ---
Does the demo in demo/ work?
I've tried to reproduce the problem but cannot. I've tried on my machine and in
the provided docker environment.
The latter gives this output when running in valgrind:
$ valgrind
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #4 from Bruno Bigras ---
==2023== Memcheck, a memory error detector
==2023== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2023== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==2023== Command: ./MyEx
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #3 from Jos van den Oever ---
Could you run the debug version in valgrind?
cmake -GNinja -DCMAKE_BUILD_TYPE=Debug ..
ninja
valgrind MyExe
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #2 from Bruno Bigras ---
(In reply to Jos van den Oever from comment #1)
> Does this happen at startup without any user interaction?
Yes at startup.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389419
--- Comment #1 from Jos van den Oever ---
Does this happen at startup without any user interaction?
--
You are receiving this mail because:
You are watching all bug changes.
21 matches
Mail list logo
