Java VM: OpenJDK Client VM (24.80-b11 mixed mode haiku-x86 )
Problematic frame:
C [libnet.so+0xef71] _fini+0x0
I have a crash report for the application failure, but don't know where to submit it. This forum is obviously an inapproprate place to report a bug, yet the Haiku Depot app usually does not make any reference about who is responsible for the port. It usually just says "no info" in the lower left hand corner of the GUI. I know I could dig through the installed files in the app install directory to try to find something, but there should be an easier way. This is a third party port, so where should the bug report go? What am I missing?
There should be an intermediary (the porter) between me and https://bugs.openjdk.java.net/. Right? If the upstream project port linkages are all kopacetic, then I can submit the bug right to the source. Even that info should be made a little more apparent to folks though, IMO. Often, with small port players, the upstream linkages are broken.
for the haiku-port-dev mailing list. Is this the best place to go? I’m sure that posting to the upstream openJDK bug system would be futile (https://bugs.openjdk.java.net). Or not? The http://www.haiku-os.org/about/teams/java page has nobody on it. A very old blog post has BrianV listed as admin for the haiku port. He was trying to hand ownership to Andrew Bachmann. Anyway, I think that Haiku Depot should be populated with info to facilitate this process a little better (I suppose that port maintainers should do that?)
The crash report suggests sending the log file to:
ports are usually built with a recipe by haikuporter. Those recipes are kept at haikuports where you can also file ‘issues’ to report bugs of packages, though normally not for bugs of the packaged app, which is after all a port. Those bugs are usually tracked on that project’s website.
You can have a look at the OpenJDK recipe and see who has been working on it by clicking the icon with the clock hands inside a count-clockwise arrow “Browse commits for this branch”. Maybe you’ll meet the guy on IRC. Sometimes, however, the one that wrote the recipe doesn’t have a clue about the workings of the packaged app, or coding in general…
I put a comment on the github.com/haikuports site for this. This problem isn’t really even a bug (it would be seen as one by a user, but it’s probably just a library mismatch), yet that brings up another question: how does Haiku Depot do version checking?
All recipes are declaring their dependencies in their recipe, see the Handling Requirements wiki (though I’m not sure how accurate exactly that entry currently is). More info on PM intricacies can be found in the Dev Wiki.
So, I guess OpenJDK was compiled as an R5 app - so that it’s useable by the gcc2-only folks (like most of the system stuff).
It’s funny. A week ago I couldn’t have given a hoot for OpenJDK on Haiku. Then I decided it would be nice to use two apps (WebSDR and Arduino) on Haiku, and suddenly it’s relevant and necessary.
Like I was telling humdinger, adding the WebSDR and Arduino apps really adds to Haiku’s usefulness for me. I guess I should be hitting the donation button about now
Here’s the link to the github:
Github requires extra auth bits to attach files, so it’s a little lame as a facility to post the bugs (reported by “regular joes”). Many operating systems have regular bug posting facilities (trac, etc) for ports. This is not directed at you. This is just a general observation, I guess.
OK, I’m being overly picky/harsh. I have to consider what the process was prior to the package management system, for handling bugs, and how much better it is now, in retrospect. Now that I know where to post a port bug, it’s all good.
