Menu

#1461 Bochs crashs with wx enabled

pending
open
nobody
None
1
2024-12-31
2023-09-23
Oliver
No

When i try to run bochs with the following configuration:

bochs 'boot:'a floppya:" image=FD13BOOT.img, status=inserted" \
  floppyb:" type=1_2" \
  memory:" guest=64, host=64" \
  config_interface:" wx" display_library:" wx" \
  keyboard:type="mf, serial_delay=250, paste_delay=100000, user_shortcut=none, keymap=/usr/share/bochs/keymaps/x11-pc-de.map, user_shortcut=ctrl-F12" \
  log:"bochsout.txt"

Bochs oftens crashs with the following error message:

(bochs-bin:10913): Gtk-CRITICAL **: 17:07:58.864: gtk_text_attributes_ref: assertion 'values != NULL' failed

(bochs-bin:10913): Gtk-CRITICAL **: 17:07:58.864: gtk_text_attributes_ref: assertion 'values != NULL' failed

If I try to start Bochs several times in a row, Bochs eventually runs. Sometimes I need to try it 3 times, sometimes 5 are necessary.

If it runs, i only get one of the above error message lines, not two:

(bochs-bin:12238): Gtk-CRITICAL **: 17:33:39.617: gtk_text_attributes_ref: assertion 'values != NULL' failed
17:33:39: Debug: OnSim2CIEvent: event type 2016 ignored

Sometimes, i get this additional error message, then bochs crashes too:

(bochs-bin:11669): Pango-CRITICAL **: 17:28:22.232: pango_layout_new: assertion 'context != NULL' failed
Segmentation fault (core dumped)

So it seems to be a timing issue.

The problem arises when i try to run bochs with wx enabled:

config_interface: wx      
display_library: wx

This problem doesn't occur, when i try to run bochs in SDL2 and textconfig mode:

config_interface: textconfig
display_library: sdl2, options=""

BTW, it would be nice, if bochs would also run in wx mode, when a SDL keyboard layout like sdl2-pc-de.map is used.
I had to switch to "x11-pc-de.map" keyboard layout to run bochs in wx mode and getting rid of some key error messages.

My operating system is Debian 12.

Discussion

  • Oliver

    Oliver - 2023-09-24

    The crash seems to result into data loss.
    I mounted a hd image in bochs when the wx options above was enabled.
    Then bochs crashed because of wx.
    When i tried to restart it with the same configuration i get now the following message:

    00000648005p[HD    ] >>PANIC<< Identify: Sector Size of 0 is in error
    

    And a message window pops up with the message:

    Device: [HD     ]
    Message: ata0-0: could not open hard drive image file 'hd_image.img'
    
     
  • Volker Ruppert

    Volker Ruppert - 2024-06-02
    • summary: Bochs crashs with vx enabled --> Bochs crashs with wx enabled
     
  • Volker Ruppert

    Volker Ruppert - 2024-12-31

    The Bochs port for wxGTK still has an issue in case the Bochs debugger is active. Without debugger I don't see issues here. I suggest to close this bug report and create an issue on Github if you still have trouble with wx Bochs.

     

Log in to post a comment.

MongoDB Logo MongoDB