I find numerous references to work in progress. Valgrind.org calls the
SPARC64/Solaris port "historical" and gives a dead link to a code
repository on Github (and the Wayback machine did not archive the code).

OF

On 26/11/2023 05:18, OrangeFish9737 wrote:
> I find numerous references to work in progress.  Valgrind.org calls the
> SPARC64/Solaris port "historical" and gives a dead link to a code
> repository on Github (and the Wayback machine did not archive the code).
>

It appears to be in 11.4:
$ pkg search valgrind
INDEX ACTION VALUE

PACKAGE
pkg.description set Valgrind is a system for debugging and
profiling. Valgrind's tool suite can automatically detect many memory
management and threading bugs, avoiding hours of frustrating
bug-hunting, making your programs more stable. It can also perform
detailed profiling to help speed up your programs.
pkg:/developer/debug/valgrind@3.18.1-11.4.63.0.1.157.0
basename file usr/bin/valgrind


pkg:/developer/debug/valgrind@3.18.1-11.4.63.0.1.157.0
com.oracle.info.name set valgrind


pkg:/developer/debug/valgrind@3.18.1-11.4.63.0.1.157.0
pkg.fmri set solaris/developer/debug/valgrind


pkg:/developer/debug/valgrind@3.18.1-11.4.63.0.1.157.0

On 2023-11-25 22:07, Gary R. Schmidt wrote:
> On 26/11/2023 05:18, OrangeFish9737 wrote:
>> I find numerous references to work in progress.  Valgrind.org calls
>> the SPARC64/Solaris port "historical" and gives a dead link to a code
>> repository on Github (and the Wayback machine did not archive the code).
>>
>
> It appears to be in 11.4:
> $ pkg search valgrind
> INDEX                ACTION VALUE
>
>
>                            PACKAGE
> pkg.description      set    Valgrind is a system for debugging and
> profiling. Valgrind's tool suite can automatically detect many memory
> management and threading bugs, avoiding hours of frustrating
> bug-hunting, making your programs more stable. It can also perform
> detailed profiling to help speed up your programs.
> pkg:/developer/debug/valgrind@3.18.1-11.4.63.0.1.157.0
> basename             file   usr/bin/valgrind

Thank you. Unfortunately, I am running a T1, which is unsupported by 11.4.

I shall try to find the source at Oracle and try building it.

OF

On Sat, 25 Nov 2023 13:18:30 -0500, OrangeFish9737
<OrangeFish9737@invalid.invalid> wrote:
> I find numerous references to work in progress. Valgrind.org calls the
> SPARC64/Solaris port "historical" and gives a dead link to a code
> repository on Github (and the Wayback machine did not archive the code).
>
> OF

Yes, as far as I know there was a SPARC port. The dead link is to
bitbucket. Maybe it was a mercurial repo that got zapped when bitbucket
sadly dropped hg support in favour of git.

Maybe if you contact Ivo Raisr he can get you the source (perhaps
uploading to GitHub?).

Valgrind on Solaris amd64 is still maintained (and I'm doing a lot of
that maintenance). As I write this I'm checking a couple of patches that
have been provided by Oracle.

A+
Paul
--
Paul Floyd http://paulf.free.fr

On 26/11/2023 15:17, OrangeFish wrote:
> On 2023-11-25 22:07, Gary R. Schmidt wrote:
>> On 26/11/2023 05:18, OrangeFish9737 wrote:
>>> I find numerous references to work in progress.  Valgrind.org calls
>>> the SPARC64/Solaris port "historical" and gives a dead link to a code
>>> repository on Github (and the Wayback machine did not archive the code).
>>>
>>
>> It appears to be in 11.4:
>> $ pkg search valgrind
>> INDEX                ACTION VALUE
>>
>>
>>                             PACKAGE
>> pkg.description      set    Valgrind is a system for debugging and
>> profiling. Valgrind's tool suite can automatically detect many memory
>> management and threading bugs, avoiding hours of frustrating
>> bug-hunting, making your programs more stable. It can also perform
>> detailed profiling to help speed up your programs.
>> pkg:/developer/debug/valgrind@3.18.1-11.4.63.0.1.157.0
>> basename             file   usr/bin/valgrind
>
> Thank you.  Unfortunately, I am running a T1, which is unsupported by 11.4.
>
> I shall try to find the source at Oracle and try building it.
>

Good luck with getting source from Oracle :-)
However, it appears to be part of the "userland" code

https://github.com/oracle/solaris-userland/tree/master/components/valgrind

--
Bruce Porter
"The internet is a huge and diverse community but mainly friendly"
http://ytc1.blogspot.co.uk/
There *is* an alternative! http://www.openoffice.org/

On 2023-11-28 03:26, YTC#1 wrote:
> On 26/11/2023 15:17, OrangeFish wrote:
>> On 2023-11-25 22:07, Gary R. Schmidt wrote:
>>> On 26/11/2023 05:18, OrangeFish9737 wrote:
>>>> I find numerous references to work in progress.  Valgrind.org calls
>>>> the SPARC64/Solaris port "historical" and gives a dead link to a
>>>> code repository on Github (and the Wayback machine did not archive
>>>> the code).
>>>>
>>>
>>> It appears to be in 11.4:
>>> $ pkg search valgrind
>>> INDEX                ACTION VALUE
>>>
>>>
>>>                             PACKAGE
>>> pkg.description      set    Valgrind is a system for debugging and
>>> profiling. Valgrind's tool suite can automatically detect many memory
>>> management and threading bugs, avoiding hours of frustrating
>>> bug-hunting, making your programs more stable. It can also perform
>>> detailed profiling to help speed up your programs.
>>> pkg:/developer/debug/valgrind@3.18.1-11.4.63.0.1.157.0
>>> basename             file   usr/bin/valgrind
>>
>> Thank you.  Unfortunately, I am running a T1, which is unsupported by
>> 11.4.
>>
>> I shall try to find the source at Oracle and try building it.
>>
>
> Good luck with getting source from Oracle :-)

I understand -- I was hoping that valgrind being open-source and all
that, one could find the mods for Sparc.

> However, it appears to be part of the "userland" code
>
> https://github.com/oracle/solaris-userland/tree/master/components/valgrind

Unfortunately, the Makefile for that specifies: "BUILD_ARCH= i386".

So probably a dead-end for now.

You got me to look ... :) I know nothing about valgrind and have never
used it.

https://valgrind.org/downloads/old.html lists releases from 1.9.6 -
3.4.1. While these releases are no longer supported, if SPARC was ever
supported by valgrind.org itself, the RELEASE NOTES from the current
version (if valgrind comes with such a file) should say at what version
that support was removed, so then you can fetch the latest version that
still had that support.

Now, yes, if SPARC support was an Oracle local mod, that won't help.
-WBE

On 2023-11-28 13:26, Winston wrote:
> You got me to look ... :) I know nothing about valgrind and have never
> used it.
>
> https://valgrind.org/downloads/old.html lists releases from 1.9.6 -
> 3.4.1. While these releases are no longer supported, if SPARC was ever
> supported by valgrind.org itself, the RELEASE NOTES from the current
> version (if valgrind comes with such a file) should say at what version
> that support was removed, so then you can fetch the latest version that
> still had that support.

Actually, no. The Sparc port was maintained out-of-tree (see under
Historical here https://valgrind.org/info/platforms.html). The link
given to Github is dead and the Wayback Machine did not archive the
source code.

>
> Now, yes, if SPARC support was an Oracle local mod, that won't help.
> -WBE

True but if only I could find the source that was once on Github.

OF

OrangeFish <OrangeFish@invalid.invalid> quickly replied:
> https://valgrind.org/info/platforms.html
) ... The link given to Github is dead

Err, the SPARC64/Solaris link under Historical points to bitbucket, not
github. Yes, the link https://bitbucket.org/iraisr/valgrind-solaris
labelled "code repository" goes to a page that says not found OR not
accessible without logging in.

I visited the parent "https://bitbucket.org/iraisr/". It prompted me to
log in. When I didn't, the list of repositories said no repositories
available, suggesting to me that one MUST log in to get anything.
-WBE

OrangeFish <OrangeFish@invalid.invalid> writes:
> The Sparc port was maintained out-of-tree (see under Historical here

FWIW, the HTML for that page uses <h2> for both the "Out Of Tree" and
"Historical" headers, suggesting that Historical ports are not out of
tree.
-WBE

OrangeFish <OrangeFish@invalid.invalid> writes:
> The Sparc port was maintained out-of-tree (see under Historical here

Ignore my immediately prior post beginning "FWIW" if it makes it out
into the world. (I immediately tried to cancel it, but I'm not sure the
cancel worked.) You're right: the line describing the SPARC64/Solaris
port clearly says it's an out-of-tree port.
-WBE

On 2023-11-28 14:37, Winston wrote (in part):
> You're right: the line describing the SPARC64/Solaris
> port clearly says it's an out-of-tree port.
> -WBE

The Wayback Machine archived a few top layers here:
https://web.archive.org/web/20150604152847/https://bitbucket.org/iraisr/valgrind-solaris

If you click on "Source", you will see a list of directories but
anything below was not archived. Maybe, with luck, the original
maintainer may see this thread.

OF

On Tue, 28 Nov 2023 08:26:23 +0000, YTC#1 <ytc1@ytc1.co.uk> wrote:
>
> Good luck with getting source from Oracle :-)
> However, it appears to be part of the "userland" code
>
> https://github.com/oracle/solaris-userland/tree/master/components/valgrind

I merged 3 patches from the above repo into the upstream Valgrind git
repo in November.

Not exactly on par with RedHat, but better than the zero contributions
from Apple and ARM.

A+
Paul
--
Paul Floyd http://paulf.free.fr

On Tue, 28 Nov 2023 13:43:48 -0500, Winston
<wbe@UBEBLOCK.psr.com.invalid> wrote:
>
> I visited the parent "https://bitbucket.org/iraisr/". It prompted me to
> log in. When I didn't, the list of repositories said no repositories
> available, suggesting to me that one MUST log in to get anything.
> -WBE

Like I said, try contacting Ivo Raisr. He no longer works on Valgrind
but he might be able to upload the source to GitHub.

As an alternative, try contacting Petr Pavlu. He did a lot of the
initial work on amd64 Solaris for his MSc. He still does some work on
Valgrind in his spare time (working on a new Linux RISC-V port).

You can find both their e-mail addresses in the Valgrind git repo.

A+
Paul
--
Paul Floyd http://paulf.free.fr