Bug 653155 - [abrt] bochs-2.4.5-1.fc14: bx_cpu_c::fetchDecode32: Process /usr/bin/bochs was killed by signal 11 (SIGSEGV)
Summary: [abrt] bochs-2.4.5-1.fc14: bx_cpu_c::fetchDecode32: Process /usr/bin/bochs wa...
Alias: None
Product: Fedora
Classification: Fedora
Component: bochs
Version: 14
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Chris Lalancette
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:e53f1b50f184648e49fe0b17378...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-11-14 18:19 UTC by greubel
Modified: 2012-06-06 17:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-06-06 17:15:51 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (46.46 KB, text/plain)
2010-11-14 18:19 UTC, greubel
no flags Details

Description greubel 2010-11-14 18:19:10 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/bochs -q
component: bochs
crash_function: bx_cpu_c::fetchDecode32
executable: /usr/bin/bochs
package: bochs-2.4.5-1.fc14
rating: 4
reason: Process /usr/bin/bochs was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289754124
uid: 500

Very good work guys, but is it possible to fix that? Bochs should not segfault to make it possible to debug bad code.

I think there should be a pointer check here (stack trace using gdb and my own build of bochs because of the wrong .cc extension message):

Program received signal SIGSEGV, Segmentation fault.
bx_cpu_c::fetchDecode32 (iptr=0x10 <Address 0x10 out of bounds>, i=0xba4bc0, remainingInPage=<value optimized out>) at fetchdecode.cpp:2429
2429	  b1 = *iptr++;



PS: If needed I can add a floppy image containing the test kernel as well my bochsrc.

How to reproduce
1. Load my own kernel (it has bugs, I know that) in Bochs using GDB or internal debugger support.
2. In some place in my own code which I can not really debug now, is a bug, the asm(int $0) causes the segfault in bochs.
3. I guess its in my exception handler. It is something arround the video mem at 0xB8000.

Comment 1 greubel 2010-11-14 18:19:16 UTC
Created attachment 460392 [details]
File: backtrace

Comment 2 Cole Robinson 2012-06-06 17:15:51 UTC
F14 is long end of life, so closing as WONTFIX.

Note You need to log in before you can comment on or make changes to this bug.