Version-Release number of selected component: nodejs-0.10.12-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: node /bin/phantomjs /usr/lib/node_modules/phantom/shim.js 12300 crash_function: v8::internal::OS::DebugBreak executable: /usr/bin/node kernel: 3.9.8-300.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 v8::internal::OS::DebugBreak at src/platform-linux.cc:413 #1 v8::internal::OS::Abort at src/platform-linux.cc:397 #2 V8_Fatal at src/checks.cc:58 #3 CheckEqualsHelper at src/checks.h:71 #4 v8::internal::Thread::Start at src/platform-linux.cc:776 #5 AddActiveSampler at src/platform-linux.cc:1127 #6 v8::internal::Sampler::Start at src/platform-linux.cc:1306 #7 v8::internal::Logger::EnsureTickerStarted at src/log.cc:1771 #8 v8::internal::RuntimeProfiler::SetUp at src/runtime-profiler.cc:392 #9 v8::internal::Isolate::Init at src/isolate.cc:1940
Created attachment 768624 [details] File: backtrace
Created attachment 768625 [details] File: cgroup
Created attachment 768626 [details] File: core_backtrace
Created attachment 768627 [details] File: dso_list
Created attachment 768628 [details] File: environ
Created attachment 768629 [details] File: limits
Created attachment 768630 [details] File: maps
Created attachment 768631 [details] File: open_fds
Created attachment 768632 [details] File: proc_pid_status
Created attachment 768633 [details] File: var_log_messages
How can you reproduce this? The ABRT-reported command-line doesn't make sense at all. `*/bin/phantomjs` is an ELF binary, not JavaScript; and shouldn't be executed by node.
I'm sorry. I also can't reproduce this. Yes, command-line on the abrt-report doesn't make sense at all. But, I Certainly did not implement this command manually. The abrt tool doesn't leave the log on my local PC. However, I find more details on the abrt-server. Please refer https://retrace.fedoraproject.org/faf/problems/1030570/ If the problem happens to me again, I will take a close look at the cause and what command I have done, then report it.
Unfortunately, ABRT Server provides even less information than ABRT automatically added to this bug. Please do reopen this bug or file a new one if you experience this again.