Bug 228973 - devel/valgrind: 32-bit error on FreeBSD 11.1-RELEASE-p9 #0
Summary: devel/valgrind: 32-bit error on FreeBSD 11.1-RELEASE-p9 #0
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Paul Floyd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-13 06:49 UTC by Jouni Laakso
Modified: 2021-04-10 16:34 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jouni Laakso 2018-06-13 06:49:51 UTC
As in https://bugs.kde.org/show_bug.cgi?id=395246 , 

$ valgrind --version
valgrind-3.10.1

$ valgrind /bin/date 
valgrind: I failed to allocate space for the application's stack.
valgrind: This may be the result of a very large --main-stacksize=
valgrind: setting.  Cannot continue.  Sorry.

$ valgrind /bin/echo "1"
valgrind: I failed to allocate space for the application's stack.
valgrind: This may be the result of a very large --main-stacksize=
valgrind: setting.  Cannot continue.  Sorry.

The processor is more than seven years old 32-bit Intel Atom without any special features, two cores.
Comment 1 Ben Bullock 2018-09-30 00:54:06 UTC
This bug may be a duplicate of the following one:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224878
Comment 2 Walter Schwarzenfeld freebsd_triage 2019-03-09 08:39:28 UTC
Maintainership dropped ports r495096.
Comment 3 Walter Schwarzenfeld freebsd_triage 2019-03-10 11:45:22 UTC
Assign to new maintainer.
Comment 4 Paul Floyd 2020-07-30 11:41:55 UTC
This should now be fixed in devel/valgrind-devel and this item can be closed.
Comment 5 Niclas Zeising freebsd_committer freebsd_triage 2021-04-09 13:45:35 UTC
Over to new maintainer.

This is most likely fixed with the latest valgrind update, but I haven't verified.
Comment 6 Paul Floyd 2021-04-10 16:34:17 UTC
devel/valgrind and devel/valgrind-devel should both now work fairly well on i386.