https://bugs.kde.org/show_bug.cgi?id=475780
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=381819
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=435375
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=475780
--- Comment #3 from Paul Floyd ---
As a workaround:
export LD_PRELOAD=/lib64/libpthread.so.0
(or whatever is appropriate for your platform).
The problem is that the tools do not link with libpthread but they assume that
the client exe does.
I'm
https://bugs.kde.org/show_bug.cgi?id=475780
--- Comment #1 from Paul Floyd ---
Which version of libc is this with?
Do you also get the problem if you don't use -Wl,-init,activate and you call
activate via dlsym?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475780
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=475652
--- Comment #6 from Paul Floyd ---
Created attachment 162341
--> https://bugs.kde.org/attachment.cgi?id=162341=edit
Modified srmem functions file
Haven't had time to test this yet. I'll try to write some tests tonight.
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=475650
--- Comment #4 from Paul Floyd ---
It's OK now on FreeBSD and I've also checked with musl and Illumos.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475650
--- Comment #3 from Paul Floyd ---
The code fix looks OK, but I think that the configure test and regtest should
use C11 rather than C++.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475652
--- Comment #3 from Paul Floyd ---
Finally
https://elixir.bootlin.com/glibc/glibc-2.38/source/sysdeps/x86_64/multiarch/strncpy-avx2.S
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475652
--- Comment #2 from Paul Floyd ---
And
https://en.cppreference.com/w/c/string/wide/wcsncpy
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475652
--- Comment #1 from Paul Floyd ---
Python source here:
https://github.com/python/cpython/blob/84b7e9e3fa67fb9b92088d17839d8235f1cec62e/Python/fileutils.c#L2104
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475650
--- Comment #1 from Paul Floyd ---
For reference
https://en.cppreference.com/w/c/thread/thrd_create
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475650
Paul Floyd changed:
What|Removed |Added
Assignee|bart.vanassche+...@gmail.co |pjfl...@wanadoo.fr
|m
https://bugs.kde.org/show_bug.cgi?id=475652
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
CC
https://bugs.kde.org/show_bug.cgi?id=475650
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=331550
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=475634
--- Comment #2 from Paul Floyd ---
Also does it work with the simplest tool, "--tool=none"?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475634
--- Comment #1 from Paul Floyd ---
Try removing the vgdb options. Valgrind will be stopped waiting for a vgdb
connection via named pipe.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475634
Paul Floyd changed:
What|Removed |Added
Summary|valgrind is no starting |valgrind is not starting
CC
https://bugs.kde.org/show_bug.cgi?id=475498
--- Comment #1 from Paul Floyd ---
Also adding a wrapper will slightly improve error messages.
The FreeBSD implementation is
void *
reallocarray(void *optr, size_t nmemb, size_t size)
{
if ((nmemb >= MUL_NO_OVERFLOW || s
https://bugs.kde.org/show_bug.cgi?id=475498
Bug ID: 475498
Summary: Add reallocarray wrapper
Classification: Developer tools
Product: valgrind
Version: 3.22 GIT
Platform: Other
OS: FreeBSD
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=475485
Bug ID: 475485
Summary: Handbook: typo in OpenPGP link to Wikipedia
Classification: Applications
Product: kleopatra
Version: unspecified
Platform: Archlinux
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=470359
Paul Krause changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=453060
--- Comment #5 from Paul Krause ---
Still reproducible.
Please see comment 1 and 2 for how to fix.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=390871
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=390871
--- Comment #13 from Paul Floyd ---
(and for John, sorry I mistyped your name in git commit --author)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=390871
--- Comment #12 from Paul Floyd ---
Not sure what's missing. With Fedora 38 I get
Compiling valgrind-ebpf-rodata-bug v0.1.0
(/home/paulf/valgrind-ebpf-rodata-bug)
error: failed to run custom build command for `valgrind-ebpf-rodata-bug v0.1.0
(/home
https://bugs.kde.org/show_bug.cgi?id=390871
--- Comment #11 from Paul Floyd ---
(In reply to Tyson Nottingham from comment #10)
> Sure, though I'm only able to give repro steps geared towards Ubuntu.
>
> https://github.com/tgnottingham/valgrind-ebpf-rodata-bug
OK thanks, I'll tr
https://bugs.kde.org/show_bug.cgi?id=390871
--- Comment #9 from Paul Floyd ---
The problem seems to have gone away on Solaris. GCC has dropped Solaris 11.3,
and the latest build I have is
g++ (GCC) 12.0.1 20220425 (experimental)
Syill, the patch looks good so I'll test it and push
https://bugs.kde.org/show_bug.cgi?id=390871
--- Comment #8 from Paul Floyd ---
(In reply to Tyson Nottingham from comment #7)
> I ran into this issue when compiling a Rust program that uses eBPF with the
> mold linker.
Can you provide an example?
Since I originally reported this I ca
https://bugs.kde.org/show_bug.cgi?id=390871
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=396476
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=463458
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=474326
--- Comment #2 from Paul Floyd ---
The first part to fixing this is on the way upstream in gdb.
https://sourceware.org/bugzilla/show_bug.cgi?id=30927
That should fix the hangs.
There are still several issues, including
https://sourceware.org
https://bugs.kde.org/show_bug.cgi?id=468837
--- Comment #4 from Paul Stansell ---
Created attachment 162091
--> https://bugs.kde.org/attachment.cgi?id=162091=edit
Photo showing how monitor is not updating correctly.
After many weeks of problem-free running of Kubuntu 23.04, I just experien
https://bugs.kde.org/show_bug.cgi?id=468837
Paul Stansell changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #3 from Paul Stansell
https://bugs.kde.org/show_bug.cgi?id=475118
Bug ID: 475118
Summary: The PIM plugin of the Digital Clock widget causes
plasmasheel to crash when enabled
Classification: Plasma
Product: plasmashell
Version: 5.27.8
https://bugs.kde.org/show_bug.cgi?id=474326
--- Comment #1 from Paul Floyd ---
Looks like a GDB problem
(gdb) target remote | ./vgdb --wait=60 --vgdb-prefix=./vgdb-prefix-mcleak
/jenkins/jobs/oi-userland/workspace/components/developer/gdb/gdb-13.2/gdbsupport/filestuff.cc:381:
internal-error
https://bugs.kde.org/show_bug.cgi?id=474744
Paul Worrall changed:
What|Removed |Added
CC||p.r.worr...@gmail.com
--- Comment #1 from Paul
https://bugs.kde.org/show_bug.cgi?id=380269
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=188656
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=356174
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=474443
Paul Floyd changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=474443
--- Comment #12 from Paul Floyd ---
The count for "ERROR SUMMARY with 6 errors" is maintained in a global variable,
"n_errs_found" which gets modified by two functions, VG_(unique_error) and
VG_(maybe_record_error).
VG_(u
https://bugs.kde.org/show_bug.cgi?id=432801
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=472329
--- Comment #7 from Paul Floyd ---
After discussion on the gcc mailing list, because f is on the stack the
compiler can see that dereferencing the stack memory is safe and so it allows
reordering.
Valgrind assumes that all memory dereferences
https://bugs.kde.org/show_bug.cgi?id=474443
--- Comment #9 from Paul Floyd ---
Repeating the end of my previous comment:
Do you get the same result if you use --errors-for-leak-kinds=none?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458828
--- Comment #2 from Paul Worrall ---
After reproducing the bug as described, and refreshing Dolphin (F5), subsequent
creating and deleting of files using the terminal are shown in Dolphin without
clearing the other items.
Dolphin 23.08.1
KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=470368
--- Comment #1 from Paul Worrall ---
Additional info:
I've noticed that the error message says "Could not open file:///smb:///"
i.e. it seems to be prepending the current directory (the last one navigated to
in the file open dialog)
https://bugs.kde.org/show_bug.cgi?id=470896
Paul Worrall changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=472329
--- Comment #6 from Paul Floyd ---
Getting back to the problem
if (f && *f != a) {
generates
movq40(%rbx), %rax # MEM [(struct pair *)range$_M_node_264
+ 40B], SR.252
Error on next line:
cmpq%r14, %rax # f
https://bugs.kde.org/show_bug.cgi?id=472329
--- Comment #5 from Paul Floyd ---
For easy reference this is the commit that I need to look at. In particular the
FIXMEs.
Author: Julian Seward 2019-10-21 11:19:59
Committer: Julian Seward 2020-01-02 06:42:21
Parent
https://bugs.kde.org/show_bug.cgi?id=474443
--- Comment #7 from Paul Floyd ---
Not directly relevant, I work for Siemens EDA and I used to work for Synopsys.
So my facetious answer is - use QuestaSim :-)
Just some comments on the logs to start with.
Lots of the errors refer to obfuscated
https://bugs.kde.org/show_bug.cgi?id=474443
--- Comment #5 from Paul Floyd ---
(In reply to Jane from comment #4)
> (In reply to Paul Floyd from comment #3)
> > I really can't tell any more without the logs and details of what exactly
> > which process are being run.
>
>
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #66 from Paul Floyd ---
I've run the CI tests, all OK. I'll change the commit message to match typical
bugzilla fixes.
Do you want me to keep
Author: eyal0 <109809+ey...@users.noreply.github.com>
?
If you would like to contribut
https://bugs.kde.org/show_bug.cgi?id=474443
--- Comment #3 from Paul Floyd ---
I really can't tell any more without the logs and details of what exactly which
process are being run.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474497
Bug ID: 474497
Summary: Crash while saving
Classification: Applications
Product: kate
Version: 23.08.0
Platform: openSUSE
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=441879
Paul Elliott changed:
What|Removed |Added
CC||p...@niburu.org
--- Comment #5 from Paul
https://bugs.kde.org/show_bug.cgi?id=379630
--- Comment #10 from Paul Floyd ---
I still get the same error with CGG 11.2.
Your wrapper looks right to me, as long as the pthread_mutex_t is the very
first thing in the maemory layout of the std::mutex. That's the case for GCC
libstdc++ and I
https://bugs.kde.org/show_bug.cgi?id=474443
--- Comment #1 from Paul Floyd ---
This looks more like user error than a critical defect to me.
When you are using --log-file and --trace-children=yes you should really use
%p in the log file name. Otherwise the children will overwrite the log file
https://bugs.kde.org/show_bug.cgi?id=474443
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=379630
--- Comment #9 from Paul Floyd ---
There are two ways to initialize a pthread_mutex_t object:
call pthread_mutex_init() or
use the static initializer PTHREAD_MUTEX_INITIALIZER
The function way is "nice" from a Valgrind perspective si
https://bugs.kde.org/show_bug.cgi?id=379630
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=474366
--- Comment #11 from Paul Worrall ---
I experience the problem with many HEIC files.
With digiKam _not_ running on my PC, my wife used dolphin to copy the files
from her phone into folders on a NAS server which is mounted on my PC using
NFS. I have
https://bugs.kde.org/show_bug.cgi?id=467441
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=467441
Bug 467441 depends on bug 433857, which changed state.
Bug 433857 Summary: Add validation to C++17 aligned new/delete alignment size
https://bugs.kde.org/show_bug.cgi?id=433857
What|Removed |Added
https://bugs.kde.org/show_bug.cgi?id=433857
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=433859
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=466105
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=474366
--- Comment #9 from Paul Worrall ---
Rereading the metadata from the image causes the thumbnail orientation to
correct itself
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474366
--- Comment #8 from Paul Worrall ---
digikam.general: Using 2 CPU core to run threads
digikam.general: Using 1 CPU core to run threads
digikam.general: Creating a metadata task for synchronizing metadata
digikam.general: Action Thread run 1 new
https://bugs.kde.org/show_bug.cgi?id=474366
--- Comment #7 from Paul Worrall ---
Created attachment 161547
--> https://bugs.kde.org/attachment.cgi?id=161547=edit
My settings under Metadata -> Rotation
These are my settings under metadata -> rotation
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=474366
--- Comment #4 from Paul Worrall ---
libheif 1.16.2-1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #64 from Paul Floyd ---
> I think that you could have used 'git apply' also. Anyway, I hope that the
> tests are all passing now and perhaps we can make progress on the patch?
It's next on my list!
Been very busy this weekend up
https://bugs.kde.org/show_bug.cgi?id=474366
Paul Worrall changed:
What|Removed |Added
CC||p.r.worr...@gmail.com
--- Comment #3 from Paul
https://bugs.kde.org/show_bug.cgi?id=474332
--- Comment #9 from Paul Floyd ---
> I'm a dummy, I confused myself looking at the wrong ALIGNED_ALLOC (the one
> that received the modification) and missed that I had to re-run autogen.
> Sorry for the time lost.
No worry. I often make mi
https://bugs.kde.org/show_bug.cgi?id=474332
--- Comment #7 from Paul Floyd ---
With this:
char *p = aligned_alloc(3, 4);
I get
standalone:
Allocation failed!
Valgrind 3.21:
Allocation failed!
Valgrind git head:
==1279== Invalid alignment value: 3 (should be a power of 2)
==1279
https://bugs.kde.org/show_bug.cgi?id=474332
--- Comment #6 from Paul Floyd ---
Hmm. I need to check that.
There will be cases where the allocation succeeds but you get an error message.
The goal is to warn about anything that is unsafe and non-portable.
That would be the case for older glibc
https://bugs.kde.org/show_bug.cgi?id=474332
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=474332
--- Comment #4 from Paul Floyd ---
Should be fixed with this. Tested in Debian with an older libc, ArchLinux
latest and FreeBSD.
commit ae413f79b24de558ac9ab925babd1fb86e0d21c7 (HEAD -> master,
origin/users/paulf/try-bug474332, origin/master, ori
https://bugs.kde.org/show_bug.cgi?id=474366
Bug ID: 474366
Summary: HEIC thumbnail rotation
Classification: Applications
Product: digikam
Version: 8.1.0
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=474332
--- Comment #2 from Paul Floyd ---
*** Bug 474339 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474339
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=474332
Paul Floyd changed:
What|Removed |Added
Version|3.21.0 |3.22 GIT
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=474332
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=474339
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=474326
Bug ID: 474326
Summary: illumos: gdbserver tests hanging
Classification: Developer tools
Product: valgrind
Version: 3.22 GIT
Platform: Compiled Sources
OS: Unspecified
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #62 from Paul Floyd ---
OK didn't know that (or had forgotten). I think I tried git patch which didn't
like the formatted patch and then my usual fallback 'patch -p1 < patchfile'
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #59 from Paul Floyd ---
You forgot to update the expecteds (I saw that just the line numbers have
changed), and I had to convert the text .cpp files into symlinks (does Linux /
GCC accept a plain text .cpp file that just contains a path
https://bugs.kde.org/show_bug.cgi?id=438883
--- Comment #75 from Paul Hands ---
What's with removing our votes? I had one vote registered, and it was removed,
apparently because I had too many votes???!
Is this a not-so-subtle way of telling us the effect is not going to be
restored?
--
You
https://bugs.kde.org/show_bug.cgi?id=432801
--- Comment #50 from Paul Floyd ---
(In reply to Paul Floyd from comment #49)
> I'll use a try branch for this patch.
I get two failures, both x86 testcases.
== 829 tests, 2 stderr failures, 2 stdout failures, 0 stderrB failures, 0
stdoutB failu
https://bugs.kde.org/show_bug.cgi?id=473884
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=473974
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=473974
--- Comment #1 from Paul Floyd ---
I also get 3 digits with RHEL 7.9 / GCC 11.2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=473978
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=473870
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=473870
--- Comment #4 from Paul Floyd ---
Trying to see where the redir is going wrong and thinking that there is an
iFunc.
On RHEL, for instance, libc contains plenty:
nm /lib64/libc.so.6 | grep " i "
...
0008b100 i strcat
...
Just ca
https://bugs.kde.org/show_bug.cgi?id=473944
--- Comment #4 from Paul Floyd ---
I also think that it's better to have less hard coded assumptions about the
number of PT_LOAD segments. This makes one part more flexible.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=473870
--- Comment #3 from Paul Floyd ---
The last syscalls
SYSCALL[1610,1]( 5) sys_open ( 0x4825008(/lib/libc.so.7), 3145728 ) -->
[async] ...
SYSCALL[1610,1]( 5) ... [async] --> Success(0x3)
SYSCALL[1610,1](551) sys_fstat ( 3, 0x1ffbfff460
701 - 800 of 4346 matches
Mail list logo
