https://bugs.kde.org/show_bug.cgi?id=497977
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=497723
--- Comment #7 from Philippe Waroquiers ---
I pushed 2 minor demangling related changes in the user manual and in some code
comments.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=497723
--- Comment #4 from Philippe Waroquiers ---
(In reply to Paul Floyd from comment #3)
> I've unconditionally turned off Ada demangling with callgrind.
> Also added the bug497723 testcase to callgrind/tests with a grep for
> functions c
https://bugs.kde.org/show_bug.cgi?id=497723
--- Comment #2 from Philippe Waroquiers ---
(In reply to Philippe Waroquiers from comment #1)
> A small test program:
>
> ith P; use P;
Missing the leading w of the 'with P'.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=497723
--- Comment #1 from Philippe Waroquiers ---
A small test program:
ith P; use P;
procedure T is
begin
for I in 1 .. 10_000_000 loop
Proc (I);
end loop;
for I in 1 .. 5_000_000 loop
Proc (I mod 2 = 0);
end loop;
for I in 1 .. 1_000_000
https://bugs.kde.org/show_bug.cgi?id=497723
Philippe Waroquiers changed:
What|Removed |Added
CC||m...@klomp.org
https://bugs.kde.org/show_bug.cgi?id=497723
Bug ID: 497723
Summary: Enabling Ada demangling breaks callgrind
differentiation between overloaded functions and
procedures
Classification: Developer tools
Product: valgrind
https://bugs.kde.org/show_bug.cgi?id=445235
--- Comment #14 from Philippe Waroquiers ---
(In reply to Mark Wielaard from comment #10)
> So one simple question might be whether we actually want to demangle Ada?
> It looks like the mangling is so simple (. -> __, add _ada_ for &
https://bugs.kde.org/show_bug.cgi?id=445235
--- Comment #8 from Philippe Waroquiers ---
(In reply to Paul Floyd from comment #7)
> I installed gnat and I get, without any mods
>
> ==48426== 4 bytes in 1 blocks are definitely lost in loss record 1 of 2
> ==48426==at 0x484
https://bugs.kde.org/show_bug.cgi?id=490651
--- Comment #10 from Philippe Waroquiers ---
(In reply to Mark Wielaard from comment #9)
> It is definitely noticeable for me. And I have seen much longer build times
> on some non-x86_64 arches.
Effectively this gives more difference t
https://bugs.kde.org/show_bug.cgi?id=490651
--- Comment #8 from Philippe Waroquiers ---
(In reply to Sam James from comment #7)
> The reproduction instructions you used seem mixed. If you compile with
> `make` (implicit -j1), then it's essentially the same, as GCC won't
> p
https://bugs.kde.org/show_bug.cgi?id=490651
--- Comment #6 from Philippe Waroquiers ---
Note that I did at work some trials of building with and without lto, with
lto-partition=one and with the default lto partitioning,
with gcc (GCC) 12.3.1
on AMD Ryzen Threadripper PRO 5975WX 32-Cores
Red Hat
https://bugs.kde.org/show_bug.cgi?id=490651
--- Comment #3 from Philippe Waroquiers ---
(In reply to Mark Wielaard from comment #2)
> I agree with Sam that using the default partitioning algorithm seems better
> than forcing one.
> Philippe, any comments?
Looking at the comments in con
https://bugs.kde.org/show_bug.cgi?id=489040
Philippe Waroquiers changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=489040
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=489040
Bug ID: 489040
Summary: patch to show the location increasing the stack
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: Linux
S
https://bugs.kde.org/show_bug.cgi?id=479191
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=473944
Philippe Waroquiers changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=473944
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=473944
Bug ID: 473944
Summary: Handle mold linker split RW PT_LOAD segments correctly
Classification: Developer tools
Product: valgrind
Version: 3.21.0
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=88
--- Comment #7 from Philippe Waroquiers ---
(In reply to Paul Floyd from comment #6)
> > I think we should check and use the existing hint. Current users of the
> > hint
> > will/should have the same behaviour whatever the glibc v
https://bugs.kde.org/show_bug.cgi?id=88
--- Comment #5 from Philippe Waroquiers ---
(In reply to Paul Floyd from comment #4)
> Thanks for adding me to the CC Philippe.
>
> If I do this:
> export GLIBC_TUNABLES="glibc.pthread.stack_cache_size=0"
>
> Then helg
https://bugs.kde.org/show_bug.cgi?id=88
--- Comment #3 from Philippe Waroquiers ---
(In reply to Mark Wielaard from comment #2)
> (In reply to Philippe Waroquiers from comment #1)
> > In the discussion on valgrind-users mailing list,
> > Paul reported tthat:
>
https://bugs.kde.org/show_bug.cgi?id=88
Philippe Waroquiers changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=88
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=458915
Philippe Waroquiers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=460142
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #25 from Philippe Waroquiers ---
(In reply to Libor Peltan from comment #24)
> You will probably need to run the test several time until it reproduces. It
> may also happen on some machines that it does never reproduce. For me, it
&g
https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #23 from Philippe Waroquiers ---
(In reply to Libor Peltan from comment #22)
> (In reply to Philippe Waroquiers from comment #21)
> > Valgrind should stop by itself when it finds an error (when using
> > --vgdb-error arg
https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #21 from Philippe Waroquiers ---
(In reply to Libor Peltan from comment #20)
> Thank you for your observations! Based on this, we actually found out that
> the issue happens exactly (sometimes!) when we attach vgdb to the running
>
https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #19 from Philippe Waroquiers ---
I took a look at the attached logs.
A first observation:
* We have 2 groups of 3 threads that get the 0xe8 syscall return.
* For each of these 2 groups, we see a little bit before these 0xe8 return that
https://bugs.kde.org/show_bug.cgi?id=459477
Philippe Waroquiers changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #16 from Philippe Waroquiers ---
In one of the trace I see the below trace. It looks like the a signal SIGALRM
is delivered to the thread that encounters the futex 202 result.
--24048-- async signal handler: signal=14, vgtid=24051, tid=4
https://bugs.kde.org/show_bug.cgi?id=459031
Philippe Waroquiers changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #8 from Philippe Waroquiers ---
I took a look at both logs.
First the epoll log.
(tid is the an thread id number used internally in valgrind)
What we see is that the tid 14 is just getting the result of a previous epoll
syscall, and then
https://bugs.kde.org/show_bug.cgi?id=458915
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=441069
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=458118
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=457898
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=457619
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=455826
--- Comment #7 from Philippe Waroquiers ---
On Fri, 2022-06-24 at 10:06 +, shapath wrote:
> https://bugs.kde.org/show_bug.cgi?id=455826
>
> --- Comment #5 from shapath ---
> (In reply to Philippe Waroquiers from comment #4)
>
https://bugs.kde.org/show_bug.cgi?id=455826
--- Comment #4 from Philippe Waroquiers ---
(In reply to shapath from comment #3)
>
> Valgrind report:-
> ==
> (gdb) monitor leak_check full reachable any
When compiling with gcc -g -O0 and doing the leak search,
I do not get an
https://bugs.kde.org/show_bug.cgi?id=455826
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=452058
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=440765
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=435493
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=434035
--- Comment #1 from Philippe Waroquiers ---
Patch looks ok to me.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=338633
Philippe Waroquiers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=432870
Philippe Waroquiers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=432870
--- Comment #7 from Philippe Waroquiers ---
Created attachment 136473
--> https://bugs.kde.org/attachment.cgi?id=136473&action=edit
fix nlcontrolc.vgtest blocking on arm64 or newer glibc
Attach patch should fix the blockage. Tested on de
https://bugs.kde.org/show_bug.cgi?id=434057
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=432510
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=427510
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=426853
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=424656
Philippe Waroquiers changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=424656
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=417075
Philippe Waroquiers changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #11 from Philippe Waroquiers ---
Updated the warning message to be:
==3170== WARNING: preadv(vector[...]) is an obsolete suppression line not
supported anymore since valgrind 3.15.
==3170== You should replace [...] by a specific index such
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #10 from Philippe Waroquiers ---
Some further notes:
I should re-update the warning to replace the final 'or ...'
by 'or [2].
And I sincerely hope that nobody is using preadv and pwritev wrongly
with huge vectors, as other
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #9 from Philippe Waroquiers ---
Created attachment 127809
--> https://bugs.kde.org/attachment.cgi?id=127809&action=edit
not a fix, but detects the incompatible supp entry and produce a warning
The commit log explains in details
https://bugs.kde.org/show_bug.cgi?id=419562
--- Comment #3 from Philippe Waroquiers ---
(In reply to Evan Hunter from comment #2)
> Thanks for the pointers on testing it on vgdb.
> It looks like it still hangs vgdb :-(
> I too am not sure what the prctl(PR_SET_PTRACER, 1, 0, 0, 0) call
https://bugs.kde.org/show_bug.cgi?id=419562
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=418840
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #7 from Philippe Waroquiers ---
(In reply to Mark Wielaard from comment #5)
> This is unfortunate and an unforeseen consequence of making the the error
> message more useful (it is useful to know which vector contained
> uninitiali
https://bugs.kde.org/show_bug.cgi?id=417075
Philippe Waroquiers changed:
What|Removed |Added
CC||jsew...@acm.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #6 from Philippe Waroquiers ---
(In reply to Mark Wielaard from comment #5)
> This is unfortunate and an unforeseen consequence of making the the error
> message more useful (it is useful to know which vector contained
> uninitiali
https://bugs.kde.org/show_bug.cgi?id=417075
Philippe Waroquiers changed:
What|Removed |Added
CC||ahajk...@redhat.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=417075
Philippe Waroquiers changed:
What|Removed |Added
CC||m...@klomp.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=417075
--- Comment #4 from Philippe Waroquiers ---
(In reply to Leonid Yuriev from comment #3)
> > What does `valgrind --gen-suppressions=all ...` show ?
> {
>
>Memcheck:Param
>pwritev(vector[0])
>fun:pwritev
https://bugs.kde.org/show_bug.cgi?id=417075
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=413603
Philippe Waroquiers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=413603
Philippe Waroquiers changed:
What|Removed |Added
Summary|callgrind_annotate |callgrind_annotate/cg_annot
https://bugs.kde.org/show_bug.cgi?id=413603
--- Comment #5 from Philippe Waroquiers ---
(In reply to Andreas Arnez from comment #3)
> (In reply to Philippe Waroquiers from comment #2)
> > * I am wondering if we should not allow comment lines starting with
> > 0 or or spaces c
https://bugs.kde.org/show_bug.cgi?id=413603
--- Comment #2 from Philippe Waroquiers ---
Thanks for the patch.
Two small comments:
* I am wondering if we should not allow comment lines starting with
0 or or spaces characters (like empty lines?) followed by # ?
* cg_annotate seems to suffer
https://bugs.kde.org/show_bug.cgi?id=410924
--- Comment #3 from Philippe Waroquiers ---
Some feedback ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411134
Philippe Waroquiers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=411134
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=411134
Bug ID: 411134
Summary: Allow the user to change a set of command line options
during execution.
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=400593
--- Comment #5 from Philippe Waroquiers ---
(In reply to Petar Jovanovic from comment #4)
> This version looks better, thanks.
> I have just pushed it [1] after some testing, but I will leave the issue
> open so we can see over the weeken
https://bugs.kde.org/show_bug.cgi?id=410924
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=410599
--- Comment #5 from Philippe Waroquiers ---
(In reply to Stefan Maksimovic from comment #4)
> Created attachment 122077 [details]
> pth_self_kill.patch v2
>
> Thanks Philippe, validating the test through memcheck slipped my mind.
>
>
https://bugs.kde.org/show_bug.cgi?id=410599
--- Comment #3 from Philippe Waroquiers ---
(In reply to Stefan Maksimovic from comment #2)
> If it's not too much trouble, I suggest you test it yourself just to make
> sure.
I tested, and the modified test still reproduces the bug w
https://bugs.kde.org/show_bug.cgi?id=410599
--- Comment #1 from Philippe Waroquiers ---
(In reply to Stefan Maksimovic from comment #0)
> A recent commit
> https://sourceware.org/git/?p=valgrind.git;a=commit;
> h=63a9f0793113fd5d828ea7b6183812ad71f924f1
> has introduced a test wh
https://bugs.kde.org/show_bug.cgi?id=409678
--- Comment #4 from Philippe Waroquiers ---
(In reply to plasmahh from comment #3)
> > Seems there is no doc changed, no test changed.
> I wasn't aware of that its necessary to do all this, you can then close this
> ticket, I was
https://bugs.kde.org/show_bug.cgi?id=409367
--- Comment #6 from Philippe Waroquiers ---
(In reply to Allison Karlitskaya from comment #5)
> (In reply to Philippe Waroquiers from comment #4)
> > Pushed as 63a9f0793
>
> Thanks very much, Philippe.
>
> A few questions, if y
https://bugs.kde.org/show_bug.cgi?id=409678
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=409367
Philippe Waroquiers changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=409141
Philippe Waroquiers changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=409429
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=409141
--- Comment #11 from Philippe Waroquiers ---
A patch fixing this problem (and also bug 409367) has been
attached to bug 409367.
If no remarks on the approach, I will push in a few days.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=409367
--- Comment #3 from Philippe Waroquiers ---
Created attachment 121295
--> https://bugs.kde.org/attachment.cgi?id=121295&action=edit
fix hands and loops when process sends signal to itself
I have tested with the reproducer attached, and it wor
https://bugs.kde.org/show_bug.cgi?id=409367
Philippe Waroquiers changed:
What|Removed |Added
Assignee|jsew...@acm.org |philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=409367
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=409141
Philippe Waroquiers changed:
What|Removed |Added
Assignee|jsew...@acm.org |philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=255603
Philippe Waroquiers changed:
What|Removed |Added
CC||bugzilla@poradnik-webmaster
https://bugs.kde.org/show_bug.cgi?id=409162
Philippe Waroquiers changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=409141
--- Comment #9 from Philippe Waroquiers ---
See also bug https://bugs.kde.org/show_bug.cgi?id=372600
This bug seems somewhat related/similar to the above.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=409141
--- Comment #8 from Philippe Waroquiers ---
Thanks for the small reproducer.
This small test case is revealing a bunch of problems related
to termination of a process when it kills itself,
and some problems in the gdbserver debug tracing.
This last
https://bugs.kde.org/show_bug.cgi?id=409141
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
https://bugs.kde.org/show_bug.cgi?id=406434
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet
1 - 100 of 452 matches
Mail list logo
