Project

General

Profile

Bug #4355

Segmentation Fault

Added by bobgus (Bob Gustafson) over 9 years ago. Updated over 9 years ago.

Status:
Third Party's Issue
Priority:
Normal
Assignee:
-
Target version:
ruby -v:
ruby 1.9.2p136 (2010-12-25 revision 30365) [x86_64-linux]
Backport:
[ruby-core:35039]

Description

=begin
I was working in the RubyMine debugger. I think the program went off to update something in the Database (postgresql) and then I saw this report in my log file.
=end


Files

RubyBugReport (8.9 KB) RubyBugReport Copied From RubyMine/Rails log bobgus (Bob Gustafson), 02/02/2011 02:14 PM
debugBug02.txt (9.76 KB) debugBug02.txt Ruby Bug report - copied from log. bobgus (Bob Gustafson), 02/07/2011 08:03 AM

Related issues

Is duplicate of Ruby master - Bug #3826: Repeatable SEGV(seg fault) with ruby-debug19/ruby-debug-ideThird Party's Issue09/14/2010Actions
#1

Updated by bobgus (Bob Gustafson) over 9 years ago

=begin
[user1@hoho6 ~]$ gem list ruby-debug

*** LOCAL GEMS ***

ruby-debug-base19 (0.11.25.jb3, 0.11.24)
ruby-debug-ide (0.4.17.alpha, 0.4.16, 0.4.15)
ruby-debug19 (0.11.6)
[user1@hoho6 ~]$

=end

#2

Updated by bobgus (Bob Gustafson) over 9 years ago

=begin
It crashed again - I was about to start a debugging session on code that I hadn't debugged before. I am running in RubyMine.

It seems that the bug may be related to the previous bug, but perhaps the log file shows a different view..
=end

#3

Updated by bobgus (Bob Gustafson) over 9 years ago

=begin
I had set a breakpoint in code executed very early.

I took that breakpoint out and re-started the application under the debugger and it did not fail yet.

I was able to poke it with the browser, and it gave back the same result as running without the debugger (no breakpoints set).

=end

#4

Updated by naruse (Yui NARUSE) over 9 years ago

  • Status changed from Open to Third Party's Issue

It seems ruby-debug's issue.

Also available in: Atom PDF