https://bugs.kde.org/show_bug.cgi?id=390310
--- Comment #18 from Paul Floyd ---
Created attachment 180193
--> https://bugs.kde.org/attachment.cgi?id=180193&action=edit
With updated expecteds
Now clean on FreeBSD
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=390310
--- Comment #17 from Paul Floyd ---
And FreeBSD
> memcheck/tests/long_namespace_xml(stderr)
> memcheck/tests/threadname_xml(stderr)
> memcheck/tests/xml1 (stderr)
> drd/tests/annotate
https://bugs.kde.org/show_bug.cgi?id=390310
--- Comment #16 from Paul Floyd ---
As a note to myself, on Illumos I currently get the following extra fails:
> memcheck/tests/gone_abrt_xml (stderr)
> memcheck/tests/mismatches_xml(stderr)
> memcheck/t
https://bugs.kde.org/show_bug.cgi?id=497977
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=290061
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=339330
--- Comment #6 from Paul Floyd ---
I've long given up using suppressions.
I can't see how this can be fixed in Valgrind. There is instrumentation, but in
this case I think that it would need to be done within the standard library or
a
https://bugs.kde.org/show_bug.cgi?id=502263
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=420682
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=420682
--- Comment #5 from Paul Floyd ---
I've written a test for this and cleaned up the error messages a bit - there
were a few errors in the untested code.
Buildbot says I need to improve the configure.ac test the the syscall. There is
only the
https://bugs.kde.org/show_bug.cgi?id=420682
--- Comment #3 from Paul Floyd ---
Created attachment 179731
--> https://bugs.kde.org/attachment.cgi?id=179731&action=edit
initial patch
I haven't tested it yet properly, but could you try this patch?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=420682
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=420682
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=501713
--- Comment #7 from Paul Floyd ---
Does the code run cleanly with Helgrind, DRD and TSAN?
This still looks like a thread issue to me and not a memcheck issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486398
--- Comment #8 from Paul Floyd ---
The patch builds OK with no warnings on FreeBSD with clang 18.1.6. No problems
with the new tests either.
OK with sourceware build macines.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=501893
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=486398
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=501893
--- Comment #7 from Paul Floyd ---
Thanks for the examples. I can reproduce the issue. I'll push a fix and test
shortly.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=501893
--- Comment #3 from Paul Floyd ---
Created attachment 179659
--> https://bugs.kde.org/attachment.cgi?id=179659&action=edit
First go at a fix, based on strcmp.
Please could you test this patch?
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=501893
--- Comment #2 from Paul Floyd ---
Can you provide the two strings that generate this error?
On my PC with Fedora 41 wcscat is using __wcscat_evex. I don't know if that has
the same problem. That's glibc 2.40.
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=501893
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
Assignee|jsew
https://bugs.kde.org/show_bug.cgi?id=501850
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=501850
--- Comment #1 from Paul Floyd ---
I wrote a little test based on scalar
#include "scalar.h"
int main(void)
{
SY(SYS_sendfile, 1000, 2, 3, 4, 5, 6, 7, 8);
return(0);
}
I can comment out the sfMayBlock - the syscall will fail so no q
https://bugs.kde.org/show_bug.cgi?id=501850
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=501850
Bug ID: 501850
Summary: FreeBSD syscall arguments 7 and 8 incorrect.
Classification: Developer tools
Product: valgrind
Version: 3.25 GIT
Platform: Other
OS: FreeBSD
St
On 21/03/2025 09:06, kiran hardas wrote:
Hi Paul/Team,
Thank you for your suggestion. I added the entry for shmget function
in coregrind/m_syswrap/syswrap-x86-linux.c
and the error got resolved for shmget function. Yes it is x86 linux
that is getting used. Similar errors came for shmat, shmdt
https://bugs.kde.org/show_bug.cgi?id=501846
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=501846
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=501846
Bug ID: 501846
Summary: Add x86 Linux shm wrappers
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: Linux
Status: REPORTED
On 3/21/25 09:06, kiran hardas wrote:
Hi Paul/Team,
Thank you for your suggestion. I added the entry for shmget function
in coregrind/m_syswrap/syswrap-x86-linux.c
and the error got resolved for shmget function. Yes it is x86 linux
that is getting used. Similar errors came for shmat, shmdt, s
https://bugs.kde.org/show_bug.cgi?id=339330
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=501713
Paul Floyd changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=501713
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=501365
--- Comment #10 from Paul Floyd ---
(In reply to mcermak from comment #9)
> > Yes please, this code is simple enough
>
> Mark, is it really only about "hooking" the existing PRE() and POST() up?
> I've noticed that f
On 3/12/25 22:40, kiran hardas wrote:
Hi Philippe/Team,
Thank you Philippe for your suggestions, I was able to resolve the
earlier errors by adding additional valgrind options and loading the
symbol table.
In my application, few variables and a function pointer was
uninitialised which led to
https://bugs.kde.org/show_bug.cgi?id=501479
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=234814
--- Comment #5 from Paul Floyd ---
Need to look at this again.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=501479
--- Comment #2 from Paul Floyd ---
There is a bug in Illumos pthread_mutexattr_gettype
See
https://github.com/illumos/illumos-gate/blob/master/usr/src/lib/libc/port/threads/pthr_mutex.c#L370
It just reads an uninit local variable which gets
https://bugs.kde.org/show_bug.cgi?id=501479
--- Comment #1 from Paul Floyd ---
Looking at this call
pthread_mutex_init(&mutex, &mutexattr);
The type for OI and Solaris 11.4 the same but different. OI is 8 (DEFAULT) and
S11.4 is 0 (DEFAULT and NORMAL). We treat both of these the sam
https://bugs.kde.org/show_bug.cgi?id=501479
Paul Floyd changed:
What|Removed |Added
Assignee|bart.vanassche+...@gmail.co |pjfl...@wanadoo.fr
|m
https://bugs.kde.org/show_bug.cgi?id=501479
Bug ID: 501479
Summary: Illumos DRD pthread_mutex_init wrapper errors
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Compiled Sources
OS: Unspecifie
https://bugs.kde.org/show_bug.cgi?id=501365
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #3 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=501348
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving this
On 15-02-25 08:50, Paul Floyd via oi-dev wrote:
I'll be asking more questions as I try to clean up more of the
outstanding issues.
== 920 tests, 43 stderr failures, 5 stdout failures, 1 stderrB failure,
5 stdoutB failures, 0 post failures ==
Probably the most interesting bit is t
On 3/9/25 14:41, Stephan Althaus wrote:
Hello!
I have used the MSI gt 1030 in the past. (and a NVS 295)
To check compatibility, you need to look which nvidia driver version
supports that card, this is not specifically related to the OS.
The nvidia driver search gives me the version s 387.
On 3/9/25 21:33, Andreas Wacknitz via openindiana-discuss wrote:
From time to time I create new installation media for test purposes and
put them here:
https://dlc.openindiana.org/isos/hipster/test/
The latest is of today ;-)
Thanks, that worked a lot better. I now have a network connection.
On 09-03-25 21:33, Andreas Wacknitz via openindiana-discuss wrote:
https://openindiana.org/mailman/listinfo/openindiana-discuss
From time to time I create new installation media for test purposes and
put them here:
https://dlc.openindiana.org/isos/hipster/test/
The latest is of today ;-)
I'll have to put getting a working NVIDIA driver on pause for the moment.
My next problem is that ethernet doesn't get recognized. It's an Intel
I226-V (igc). From what I see that didn't get added to OI until Dec
2024, so it isn't part of the OI 2024.10 install.
The install has options to add
On 09-03-25 11:24, Andreas Wacknitz via openindiana-discuss wrote:
Look at https://www.nvidia.com/en-us/drivers/unix/
There is a list of supported drivers for Solaris x64/x86. Following the
provided links you can find a list of supported products. The lists
don't contain consumer grade cards
On 3/9/25 10:53, Paul Floyd via openindiana-discuss wrote:
I just got an MSI GT 1030 and that doesn't seem to work either (at
least the hipster 24.10 live DVD fails to load the nvidia 470 drivers).
The 550 driver works on FreeBSD. Fedora 41 and Windows 11 just worked
automatically
Hi
Hi
You could get a used NVIDIA quadro NVS that you can use with package
nvidia-340,
or an nvidia GT 1030 - both should come without fan so very silent 0db.
I see prices around 80-90€ for a GT 1030, you probably could get a
newer card for the same money if you're lucky..
I just got an
https://bugs.kde.org/show_bug.cgi?id=501194
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=234814
--- Comment #6 from Paul Floyd ---
(In reply to Paul Floyd from comment #5)
> Need to look at this again.
Works fine on FreeBSD. I need to go through my git history between 2020-04-13
(when it wasn't working on FreeBSD) and 2021-10-03 (whe
https://bugs.kde.org/show_bug.cgi?id=501194
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=501194
Bug ID: 501194
Summary: Fix ML_(check_macho_and_get_rw_loads) so that it is
correct for any number of segment commands
Classification: Developer tools
Product: valgrind
Version: 3.24 GI
https://bugs.kde.org/show_bug.cgi?id=271582
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=339160
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=271582
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=486398
--- Comment #5 from Paul Floyd ---
Thanks for the patch. I'm busy at the moment setting up a new PC. It might take
some time. I'll take a look when that's all done.
--
You are receiving this mail because:
You are watching all bug changes.
On 2/21/25 22:03, John D Groenveld via openindiana-discuss wrote:
In message<55759f1f-1900-4188-8cf4-677538b39...@wanadoo.fr>, Paul Floyd via op
enindiana-discuss writes:
For the moment the PC has Fedora, Windows and FreeBSD on it. Fedora and
Windows are using the AMDGPU for graphics
Hi
I just tried booting OpenIndiana Hipster 2024.10 on a new PC (AMD Ryzen
9 9900X, Asus Rog Strix X870-A), no video card).
I got as far as choosing the language and trying to start video mode,
which failed. That's not too much of a problem - I can always install
with the text mode installer
On 2/20/25 12:03, David Chisnall wrote:
No, that’s always been the case in C++. It comes from the rule that two
allocations must have unique addresses. If a structure could have size zero,
an array of these structures would have size zero and the two elements in the
array would have the sa
On 15-02-25 08:50, Paul Floyd via oi-dev wrote:
I'll be asking more questions as I try to clean up more of the
outstanding issues.
My first question isn't a Valgrind question, it's a testcase that's
problematic.
The source file is here
https://sourceware.org/git/?p
On 15-02-25 18:58, s...@telenet.be wrote:
valgrind can run the OpenSmalltalk (a dialect or fork of Squeak) interpreter on
OpenIndiana.
I reported a bug (not sure this is really a bug) for it #17199.
This relates to https://illumos.org/man/7/epoll because epoll can be enabled
for OpenSma
On 15-02-25 15:09, John Paul Adrian Glaubitz wrote:
Slightly off-topic, but does anyone have a copy of the Valgrind git repository
which contains the port to sparcv9?
Try asking Ivo Raisr or Petr Pavlu
Ivo Raisr
Petr Pavlu
(maybe try petr.pavlu instead of setup for Petr).
A+
Paul
On 15-02-25 11:33, Till Wegmüller wrote:
Hey Paul
Looking forward to your contribution. Here is the documentation for
Packaging your Valgrind port. https://docs.openindiana.org/dev/userland/
#a-component-usually-consists-of-several-files If you need a Vagrant box
I Maintain those :)
Hi
P
On 15-02-25 10:01, Andreas Wacknitz via oi-dev wrote:
Phantastic, welcome to OpenIndiana and illumos!
I'm not exactly new to OpenIndiana. I used Solaris SPARC as my main work
machine for about 15 years and my main home machine (amd64) for a bit
longer. These days it's Linux at work and ma
Hi
Just joined the list, and by coincidence I saw
Am 12.01.25 um 10:48 schrieb Cedric Blancher:
> Good morning!
>
> Does OpenIndiana have a valgrind package? Illumos/x86-64 is supported
> by valgrind
>
> Ced
╰─➤ pkg list -a|grep valgrind
developer/debug/valgrind 3.22.0-2023.0.0.0 ---
https://bugs.kde.org/show_bug.cgi?id=496370
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=496370
--- Comment #5 from Paul Floyd ---
I'll try
#pragma GCC push_options
#pragma GCC optimize ("O0")
void VG_(save_context)(ThreadId tid, vki_ucontext_t *uc, CorePart part)
...
#pragma GCC pop_options
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=496370
--- Comment #4 from Paul Floyd ---
I've tried a GCC 12 build of Valgrind with both a GCC 4.8.2 and GCC 12 built
versions of signal2 and they both crash. So it's not a change in the
compilation of the testcase that's the problem.
Next, i
On 10-02-25 09:44, Lev Yudalevich wrote:
My first PC has i7-6700K @ 4.00GHz x 8 CPU, 32GiB RAM
My second PC has i7-10700 @ 2.90GHz x 16 CPU, 64GiB RAM
Both machines have identical OS installation (Ubuntu 22.04.5 LTS) rest
of the software (toolchains etc).
However, running Valgrind (version 3.
> On 11 Feb 2025, at 04:38, Jessica Long wrote:
>
> Not sure what to do. I'm new to Linux and Valgrind.
>
> I'm on CLion, and I'm trying to run my code with Valgrind memcheck. However
> I get the message.
>
> --33110:0:libcfile Valgrind: FATAL: Private file creation failed.
>The curre
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #15 from Paul Floyd ---
(In reply to Geoffrey Thomas from comment #14)
> Compiled from Git and it appears to work the way I expect on Linux. Thanks!
>
> # ../valgrind/vg-in-place --tool=none -q ./script
> Hello world!
Just
https://bugs.kde.org/show_bug.cgi?id=396415
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #12 from Paul Floyd ---
Created attachment 178008
--> https://bugs.kde.org/attachment.cgi?id=178008&action=edit
Patch for Linux
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #11 from Paul Floyd ---
After a bit of trying to battle with load_client() where we were VG_(open)'ing
"exe_name" (which could be a script with/without a shebang, and the shebang
could refer to another script [which could rep
https://bugs.kde.org/show_bug.cgi?id=499561
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #10 from Paul Floyd ---
And fixing AT_EXECFN doesn't help on Linux (though we should probably do that
one day).
I think that we need to resolve the linked path before opening VG_(cl_exec_fd).
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #9 from Paul Floyd ---
Created attachment 177987
--> https://bugs.kde.org/attachment.cgi?id=177987&action=edit
Patch for FreeBSD
Initial patch for FrfeeBSD. I also have a test (based on the existing auxv
test), not included in thi
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #8 from Paul Floyd ---
Looking some more, on FreeBSD t looks like we're setting AT_EXECPATH to the
script name as follows
const HChar *exe_name = VG_(find_executable)(VG_(args_the_exename));
HChar resolved_name[VKI_PATH_MAX];
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #7 from Paul Floyd ---
Just had a quick look on FreeBSD. It looks like it's just using __realpathat on
/path/link/main which, being a link, resolves to /path/orig/main, and then
getdirentries. Under Valgrind it's calling _rea
https://bugs.kde.org/show_bug.cgi?id=396415
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=496972
--- Comment #1 from Paul Floyd ---
The first error happens very early on.
Running under vgdb and using step-instruction to get back somewhere with a
stack
#0 0x08523e0d in ?? () from /usr/local/lib/libpcre2-16.so.0
#1 0x08523d46 in
https://bugs.kde.org/show_bug.cgi?id=396415
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #5 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=471802
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #21 from Paul
https://bugs.kde.org/show_bug.cgi?id=499183
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=499183
--- Comment #2 from Paul Floyd ---
I think that I see the problem.
GEN_test_RandM(VMOVQ_XMM_to_XMM_LOW_LOW_HIGH,
"vmovq %%xmm0, %%xmm7; vmovq %%xmm8, %%xmm0",
"vmovq %%xmm0, (%%rsi); vmovq %%xmm9, %%xmm0&
https://bugs.kde.org/show_bug.cgi?id=499212
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=499212
Paul Floyd changed:
What|Removed |Added
Summary|mmap() with MAP_ALIGNED() |mmap() with MAP_ALIGNED
https://bugs.kde.org/show_bug.cgi?id=499212
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
Assignee|jsew
https://bugs.kde.org/show_bug.cgi?id=499183
Bug ID: 499183
Summary: FreeBSD: differences in avx-vmovq output
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: FreeBSD Ports
OS: FreeBSD
https://bugs.kde.org/show_bug.cgi?id=499183
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=499183
--- Comment #1 from Paul Floyd ---
paulf@green:~/test/valgrind/none/tests/amd64 $ cat avx-vmovq.stdout.diff
--- avx-vmovq.stdout.exp2025-01-26 16:09:27.689155000 +0100
+++ avx-vmovq.stdout.out2025-01-26 22:39:32.558711000 +0100
@@ -87,7
https://bugs.kde.org/show_bug.cgi?id=492678
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=492678
--- Comment #8 from Paul Floyd ---
OK, I modified the testcase to use timer_create/timer_delete and reproduced
both the error and the fix on Linux. I couldn't reproduce the error with
FreeBSD. I'll try to push a fix and 2 testcases th
https://bugs.kde.org/show_bug.cgi?id=498936
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=498936
--- Comment #3 from Paul Floyd ---
(In reply to Tavian Barnes from comment #2)
> --fair-sched=yes seems to work around it
OK, can we close this item?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492678
--- Comment #6 from Paul Floyd ---
(In reply to Tavian Barnes from comment #3)
> I think this should fix it:
>
> diff --git a/coregrind/m_syswrap/syswrap-linux.c
> b/coregrind/m_syswrap/syswrap-linux.c
> index e8978b5bc..83af91344
https://bugs.kde.org/show_bug.cgi?id=492678
--- Comment #5 from Paul Floyd ---
And on Fedora (same PC) I had to increase the timer period to reproduce the
problem. The same change PRE(sys_setitimer) also seems to fix it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492678
--- Comment #4 from Paul Floyd ---
This works for me on FreeBSD
diff --git a/coregrind/m_syswrap/syswrap-freebsd.c
b/coregrind/m_syswrap/syswrap-freebsd.c
index d358c90eb..339724938 100644
--- a/coregrind/m_syswrap/syswrap-freebsd.c
+++ b/coregrind
1 - 100 of 1354 matches
Mail list logo
