[valgrind] [Bug 393415] Valgrind memory debugging for nodejs using child process failed on MacOS

[Paul Floyd]

https://bugs.kde.org/show_bug.cgi?id=393415

Paul Floyd  changed:

   What|Removed |Added

 CC||pjfl...@wanadoo.fr

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 393415] Valgrind memory debugging for nodejs using child process failed on MacOS

[Rhys Kidd]

https://bugs.kde.org/show_bug.cgi?id=393415

--- Comment #2 from Rhys Kidd  ---
Any further feedback Nazar?
Will close this report unless able to establish this is indeed a Valgrind bug,
not an application bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 393415] Valgrind memory debugging for nodejs using child process failed on MacOS

[Rhys Kidd]

https://bugs.kde.org/show_bug.cgi?id=393415

Rhys Kidd  changed:

   What|Removed |Added

 CC||rhysk...@gmail.com
   Assignee|jsew...@acm.org |rhysk...@gmail.com

--- Comment #1 from Rhys Kidd  ---
I think your code may have a subtle bug in it. To test this can you run in a
Terminal window within the relevant testing folder:

// How does the program loader find the JS interpreter?
$ ./worker

I believe your main.js should be changed as follows:

> - var child = cp.fork('./worker');
> + var child = cp.fork('worker.js');

-- 
You are receiving this mail because:
You are watching all bug changes.