https://bugs.kde.org/show_bug.cgi?id=450952
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=383010
Mark Wielaard changed:
What|Removed |Added
CC||paola_...@libero.it
--- Comment #86 from Mark
https://bugs.kde.org/show_bug.cgi?id=460203
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=383010
Mark Wielaard changed:
What|Removed |Added
CC||ktstngubl...@bugfoo.com
--- Comment #85 from
https://bugs.kde.org/show_bug.cgi?id=468544
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=383010
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Alias
https://bugs.kde.org/show_bug.cgi?id=468556
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=87
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=464609
Mark Wielaard changed:
What|Removed |Added
CC||rasters...@gmail.com
--- Comment #3 from Mark
https://bugs.kde.org/show_bug.cgi?id=461926
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Resolution
https://bugs.kde.org/show_bug.cgi?id=439685
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=439685
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
https://bugs.kde.org/show_bug.cgi?id=419054
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=464680
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=393062
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=398649
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=87
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=468556
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=464671
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #7 from Mark
https://bugs.kde.org/show_bug.cgi?id=467036
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
CC
https://bugs.kde.org/show_bug.cgi?id=467714
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=467839
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=374814
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #2 from Mark
https://bugs.kde.org/show_bug.cgi?id=459392
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=464609
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
CC
https://bugs.kde.org/show_bug.cgi?id=434057
Mark Wielaard changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=434057
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Assignee|jsew...@acm.org
https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #25 from Mark Wielaard ---
(In reply to Tom Tromey from comment #22)
> (In reply to Paul Floyd from comment #21)
>
> > I also tried to make the startup even easier and after searching a bit and
> > getting some in
https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #24 from Mark Wielaard ---
(In reply to Paul Floyd from comment #21)
> It seems quite intermittent. I've only reproduced it once, and without
> debug/verbose.
Too bad, those are the worst bugs to debug.
> I had a very q
https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #20 from Mark Wielaard ---
I wonder if there is still a timing issue if it works with extra verbose/debug
output. We tried to remove any explicit waiting/spinning.
Could you show a full session (gdb command line plus arguments and gdb
https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #16 from Mark Wielaard ---
Thanks, last patch looks pretty nice.
I threw it at the try builder and it at least compiles cleanly:
https://builder.sourceware.org/buildbot/#/changes/23263
That of course is all different GNU/Linux setups, maybe
https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #12 from Mark Wielaard ---
(In reply to Paul Floyd from comment #11)
> When I saw this
>
> +/* For accept4 and execvpe. */
> +#define _GNU_SOURCE
> #include "vgdb.h"
>
> I had a bit of a bad feeling, w
https://bugs.kde.org/show_bug.cgi?id=467714
--- Comment #2 from Mark Wielaard ---
Tested with:
#include
#include
int main (int argc, char *const argv[])
{
for (int i = 0; i < 100; ++i)
dup (1);
execvp (argv[1], argv + 1);
exit (1);
}
gcc -o dup100 dup100.c
./dup
https://bugs.kde.org/show_bug.cgi?id=467714
Mark Wielaard changed:
What|Removed |Added
Assignee|jsew...@acm.org |m...@klomp.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=436413
--- Comment #21 from Mark Wielaard ---
Looks good to me.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466172
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #2 from Mark
https://bugs.kde.org/show_bug.cgi?id=465435
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #11 from Mark
https://bugs.kde.org/show_bug.cgi?id=457504
--- Comment #14 from Mark Wielaard ---
(In reply to Feiyang Chen from comment #12)
> Most of these files were introduced by the v4-0104 patch.
> I don't know why these empty files are missing :)
> Or can I just remove them from my l
https://bugs.kde.org/show_bug.cgi?id=465465
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #6 from Mark
https://bugs.kde.org/show_bug.cgi?id=452758
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=464969
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #2 from Mark
https://bugs.kde.org/show_bug.cgi?id=436413
--- Comment #16 from Mark Wielaard ---
diff --git a/coregrind/m_syswrap/syswrap-freebsd.c
b/coregrind/m_syswrap/syswrap-freebsd.c
index 401a7ba8e..13d3b6bf2 100644
--- a/coregrind/m_syswrap/syswrap-freebsd.c
+++ b/coregrind/m_syswrap/syswrap-freebsd.c
https://bugs.kde.org/show_bug.cgi?id=436413
--- Comment #15 from Mark Wielaard ---
...checking header files and include directives
*** File coregrind/m_replacemalloc/vg_replace_malloc.c must not include
pub_tool_options.h
Only core headers are allowed in non-tool source files.
I assume
https://bugs.kde.org/show_bug.cgi?id=436413
Mark Wielaard changed:
What|Removed |Added
Attachment #155510|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=436413
Mark Wielaard changed:
What|Removed |Added
Attachment #155503|1 |0
is obsolete
https://bugs.kde.org/show_bug.cgi?id=436413
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=464680
Bug ID: 464680
Summary: Show issues caused by memory policies like selinux
deny_execmem
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=464185
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=464185
--- Comment #3 from Mark Wielaard ---
*** Bug 464184 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=464184
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=464185
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #2 from Mark
https://bugs.kde.org/show_bug.cgi?id=381819
Mark Wielaard changed:
What|Removed |Added
CC||ikoro...@gmail.com
--- Comment #27 from Mark
https://bugs.kde.org/show_bug.cgi?id=463992
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC
https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #8 from Mark Wielaard ---
We reviewed (about half) of the patch and found a couple of things to cleanup:
- There is a sleep(3) after fork, before execve in the parent (vgdb) to wait
for valgrind to fully startup
This should be replaced
https://bugs.kde.org/show_bug.cgi?id=462007
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=88
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=351857
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=459476
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=450705
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=452758
Mark Wielaard changed:
What|Removed |Added
CC||jojo19@gmail.com
--- Comment #48 from Mark
https://bugs.kde.org/show_bug.cgi?id=457412
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #10 from Mark Wielaard ---
(In reply to f.roe...@magmasoft.de from comment #9)
> Thank you for your answer. The problem occurs in the Intel 2021.6 MPI
> library. As far as I understand it runs this code path when cpuid returns
>
https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #8 from Mark Wielaard ---
(In reply to f.roe...@magmasoft.de from comment #6)
> Is this also a forbidden instruction?
> vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7C 0x48 0x10 0x2
> 0x49 0x81 0xC0 0x0
> vex amd
https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #4 from Mark Wielaard ---
(In reply to f.roe...@magmasoft.de from comment #3)
> Thank you for your answer, is there a possible workaround to get valgrind
> running?
> Is there a time schedule for a new valgrind build which fixes t
https://bugs.kde.org/show_bug.cgi?id=456948
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=424248
Mark Wielaard changed:
What|Removed |Added
CC||f.roe...@magmasoft.de
--- Comment #3 from Mark
https://bugs.kde.org/show_bug.cgi?id=456948
Mark Wielaard changed:
What|Removed |Added
Summary|Unrecognized instruction|Unrecognized instruction
https://bugs.kde.org/show_bug.cgi?id=455651
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
https://bugs.kde.org/show_bug.cgi?id=454040
--- Comment #8 from Mark Wielaard ---
I believe this is good to go. I have been testing it, including the new
testcase on various fedora systems.
Andreas, could you push the fix. Let me know if you want me to add the testcase
separately.
--
You
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #45 from Mark Wielaard ---
(In reply to Nick Nethercote from comment #35)
> With the additional commits things are working again for Rust code, thanks!
And that was without some of the patches been pushed yet :)
Could you test ag
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #44 from Mark Wielaard ---
(In reply to Lubos Lunak from comment #42)
> I don't see the dwarf spec being specific on how to interpret this, but then
> I think my way is the only logical one.
Yes, I keep getting confused. We onl
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #43 from Mark Wielaard ---
(In reply to Lubos Lunak from comment #42)
> > It looks almost correct. I would just remove the following debug (TD3) part
> > from get_debug_addr_entry_common:
>
> Updated.
Thanks,
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #40 from Mark Wielaard ---
(In reply to Lubos Lunak from comment #38)
> > imho to use #if defined(VG_BIGENDIAN) instead of doing a runtime trick.
>
> Updated.
Thanks, looks good.
> > Is the big endian variant correct?
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #39 from Mark Wielaard ---
(In reply to Lubos Lunak from comment #38)
> > But the error handling in get_debug_addr_entry looks off.
> > The second argument is DW_FORM form. But it is given either a DW_FORM,
> > DW_LLE or D
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #34 from Mark Wielaard ---
For support DW_FORM_addrx3 and DW_FORM_strx3 it would be easier/clearer imho
to use #if defined(VG_BIGENDIAN) instead of doing a runtime trick.
Is the big endian variant correct?
return c1 << 16 | c2 <
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #33 from Mark Wielaard ---
treat DW_TAG_skeleton_unit like DW_TAG_compile_unit looks good, pushed as:
commit e95904b99c87606eae1372ee4661e9db03833f08
Author: Luboš Luňák
Date: Tue Apr 26 08:35:16 2022 +0200
treat
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #32 from Mark Wielaard ---
For "implement support for missing DW_LLE_* and DW_RLE_* values" the code looks
good.
But the error handling in get_debug_addr_entry looks off.
The second argument is DW_FORM form. But it is given either
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #30 from Mark Wielaard ---
(In reply to Lubos Lunak from comment #28)
> The 7 patches should be applied in the order they
> are attached. You appear to be applying them based on their subject line,
> but those got meaning
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #29 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #27)
> But this also handles DW_FORM_rnglistx and DW_FORM_loclistx.
> Shouldn't setup_cu_bases also handle these?
And that is what patch4 does.
> And if so, shoul
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #27 from Mark Wielaard ---
Patch3 looks correct on its own. So I'll push it as is:
commit 383f36462fdc25a0e849391cf845e22703a95c08
Author: Luboš Luňák
Date: Mon Apr 25 22:11:27 2022 +0200
avoid warning about missing DW_AT_*_base
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #26 from Mark Wielaard ---
Patch 2 doesn't handle DW_AT_GNU_addr_base, DW_FORM_GNU_addr_index and
DW_FORM_GNU_str_index. But those are only used as extensions to DWARF4 with
split-dwarf. Support could be added later if people really use pre
https://bugs.kde.org/show_bug.cgi?id=452758
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Assignee|pjfl...@wanadoo.fr
https://bugs.kde.org/show_bug.cgi?id=452802
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #6 from Mark Wielaard ---
There is a fork on sourcehut that contains the start of work on a --multi
option for vgdb that implements extended-remote mode so that vgdb can start a
valgrind process in response to a vrun packet. Currently
https://bugs.kde.org/show_bug.cgi?id=452802
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #15 from Mark
https://bugs.kde.org/show_bug.cgi?id=454040
--- Comment #7 from Mark Wielaard ---
(In reply to Andreas Arnez from comment #5)
> Created attachment 149025 [details]
> Patch for adding a memmem intercept, version 2
>
> This addresses Mark's comment and removes the 'hh' variable.
Look
https://bugs.kde.org/show_bug.cgi?id=454040
Mark Wielaard changed:
What|Removed |Added
Attachment #149008|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=453602
--- Comment #2 from Mark Wielaard ---
I saw that cmdline1/2 tests failing on freebsd. That is because the new command
line flag isn't available there. I added alternative .exp files
commit 2dad922aba5998441f41f8af8c777d3771c189c4
Author: Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=453602
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=454040
--- Comment #3 from Mark Wielaard ---
Created attachment 149008
--> https://bugs.kde.org/attachment.cgi?id=149008=edit
Add memcheck memmem vgtest
I wrote a testcase that fails before the patch (on s390x) and succeeds
afterwards. It would be n
https://bugs.kde.org/show_bug.cgi?id=454040
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #2 from Mark
https://bugs.kde.org/show_bug.cgi?id=434764
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=434764
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=434764
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugzilla.redhat.com
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #22 from Mark Wielaard ---
I am really happy to see these patches. But have not read them yet. Also I am
on vacation till next week. Sorry for being slow,
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452758
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=451878
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=452722
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=450962
--- Comment #3 from Mark Wielaard ---
commit 4c27f0f7649eb02336dcd0af9d2f8977b20d3a9f
Author: Mark Wielaard
Date: Mon Apr 11 14:45:49 2022 +0200
Extend helgrind suppression for _IO_*xsputn* FILE* state manipulation
commit 7b5867b1f
https://bugs.kde.org/show_bug.cgi?id=452058
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
201 - 300 of 1207 matches
Mail list logo
