有人尝试向 Sun 提交 hs_err 文件吗?

发布于 2024-08-03 04:06:47 字数 656 浏览 13 评论 0原文

我在服务器上运行了大量 Java 代码,偶尔会出现 JVM 崩溃,并伴有故障转储 hs_err_pid 文件。

最近我决定努力做一个更好的网友,所以我检查了最新的崩溃日志,确保它确实是最新的JVM,并且崩溃不是由外部库引起的,然后我尝试将文件提交到Sun 的错误数据库

但是,整个提交过程似乎旨在阻止您提交错误报告,确保您选中该框以验证您了解这不是获得支持的地方,并强迫您填写他们实际上可以从崩溃文件中获得的所有信息,以及一些完全不相关的信息,例如我的公司名称和 Sun 帐户 ID。

所以我的问题是双重的:

  1. 是否有一些后门,通过它我可以说,“看,这是一个崩溃日志,用它做你喜欢做的事”?
  2. 我还应该打扰吗? Sun 似乎在暗示他们已经有足够的错误报告,并且他们并不真正需要人们向他们发送更多崩溃日志文件。

我应该怎么办?

编辑:如果我说得不够清楚,我只是想帮助 Sun 和社区。我不期望任何修复、解释或支持。

另一方面,我不太关心这些崩溃,根本没有精力去重现它们或调查它们。

I run a lot of java code on my servers, and occasionally I get a JVM crash, accompanied by a crash dump hs_err_pid file.

Lately I've decided to try to be a better netizen, so I examined the latest crash log, made sure it was indeed the latest JVM, and that the crash was not caused by an external library, and then I tried submitting the file to Sun's bug database.

However, it seems that the entire submitting process is geared towards preventing you from submitting bug reports, making sure you check the box to verify you understand that THIS IS NOT A PLACE TO RECEIVE SUPPORT, and forcing you to fill all this information that they could actually get from the crash file, and some more completely irrelevant information like my company name and Sun account ID.

So my question is twofold:

  1. Is there some backdoor through which I can just say, "look, here's a crash log, do what you like with it"?
  2. Should I even bother? It seems that Sun is hinting that they have enough bug reports as it is, and they don't really need people sending them more crash log files.

What should I do?

EDIT: In case I wasn't clear enough, I'm just trying to help Sun and the community. I don't expect any fixes, explanations or support.

On the other hand, I don't care enough about these crashes to put any effort into reproducing them or investigating them at all.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

柳絮泡泡 2024-08-10 04:06:48

我愿意,但前提是我理解(希望?)这只是为了更大的利益。我从未收到回复或跟进。

但是,似乎整个
提交过程旨在
阻止您提交错误
报告,确保选中该框
验证您是否了解这是
不是获得支持的地方,并且
强迫你去填补这一切
他们实际上可以的信息
从崩溃文件中获取,以及更多
完全不相关的信息,例如
我的公司名称和 Sun 帐户 ID。

我的解读是,它旨在“设定期望”。我确信,尽管你抱怨这个过程,仍有无数人提交了一份报告,然后期望詹姆斯·高斯林本人在不到两个小时内收到一封包含补丁或解决方法的电子邮件。

联系信息可能是假想的 Sun 工程师的信息,他实际上想就该报告与您联系并提出其他问题。

不要忘记 Sun 有付费支持计划,并且此崩溃报告系统不是 Sun 客户应该获得支持的地方。

因此,直接回答您的问题:

  1. 使用前门。你为什么不呢?
  2. 是的,你应该费心。只是不要期待任何反馈。

I do, but only with the understanding (hope?) that this is only for the greater good. I have never received a response or follow up.

However, it seems that the entire
submitting process is geared towards
preventing you from submitting bug
reports, making sure you check the box
to verify you understand that THIS IS
NOT A PLACE TO RECEIVE SUPPORT, and
forcing you to fill all this
information that they could actually
get from the crash file, and some more
completely irrelevant information like
my company name and Sun account ID.

My read is that it is geared toward 'setting expectations'. I'm sure there are, despite the process you complain about, zillions of folks who submit a report and then expect a person email from James Gosling himself in under two hours with a patch or workaround.

The contact info stuff is probably for a hypothetical Sun engineer that actually wants to contact you about the report with other questions.

Don't forget that Sun has a paid support programs, and that this crash report system is not where Sun customers are supposed to get support.

So, to directly answer your questions:

  1. Use the front door. Why wouldn't you?
  2. Yes, you should bother. Just don't expect any feedback.
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文