Bug #4355
closedSegmentation Fault
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
Updated by bobgus (Bob Gustafson) almost 14 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
Updated by bobgus (Bob Gustafson) almost 14 years ago
- File debugBug02.txt debugBug02.txt added
=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
Updated by bobgus (Bob Gustafson) almost 14 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
Updated by naruse (Yui NARUSE) over 13 years ago
- Status changed from Open to Third Party's Issue
It seems ruby-debug's issue.