Bug 37804 - Java VM crashed (SIGSEGV), pointing the finger at [libdbus-1.so.3+0x284e0] char+0x284e0
Summary: Java VM crashed (SIGSEGV), pointing the finger at [libdbus-1.so.3+0x284e0] c...
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: 1.2.x
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Havoc Pennington
QA Contact: John (J5) Palmieri
Depends on:
Reported: 2011-05-31 18:23 UTC by c.leonard
Modified: 2011-06-01 01:47 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

dump from Java VM (68.81 KB, text/x-log)
2011-05-31 18:23 UTC, c.leonard

Description c.leonard 2011-05-31 18:23:21 UTC
Created attachment 47409 [details]
dump from Java VM

Running Java application Biomart (https://code.oicr.on.ca/svn/biomart/biomart-java/branches/release-0_8-candidate_6/), activity at time of crash unknown. Dump is attached.

libdbus from RHEL 6:

dbus-libs.i686    1:1.2.24-4.el6_0    rhel-x86_64-server-6
Comment 1 Thiago Macieira 2011-06-01 01:47:00 UTC
Sorry, nothing we can do about this. There's no enough information in the bug report to point to a bug in libdbus-1. We need a backtrace of the native side with full symbols and/or a testcase in C.

I also know that the DBus-Java implementation doesn't use libdbus-1, so it isn't a DBus-Java issue. Given the Java stacktrace, I'd guess that the implementation of the function that proxies has a bug. Hence, this is not our bug.

Please report to whomever implemented that proxy-finding function.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.