Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#33977 - [dosbox] DOSBox debugger not installed

Attached to Project: Community Packages
Opened by Adam Nielsen (Malvineous) - Saturday, 23 February 2013, 08:03 GMT
Last edited by Maxime Gauduin (Alucryd) - Thursday, 22 August 2013, 16:13 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The DOSBox package only supplies a DOSBox binary with the DOSBox debugger compiled out. This means if you want to debug DOS programs, you have to compile DOSBox from source yourself.

Since the debugger launches automatically and can slow down applications, it would be nice if the package installed two binaries, "dosbox" and "dosbox-debug", the latter containing the debugger.

This would require compiling the source twice, the second time with "--enable-debug" passed to configure, but it would allow the best of both worlds.
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Thursday, 22 August 2013, 16:13 GMT
Reason for closing:  Won't implement
Comment by Adam Nielsen (Malvineous) - Saturday, 23 February 2013, 22:13 GMT
I've attached a patch to the PKGBUILD file which does this. It allows you to launch dosbox-debug from the command line to access the debugger.
   dosbox-debug-pkgbuild.patch (1 KiB)
Comment by Maxime Gauduin (Alucryd) - Thursday, 22 August 2013, 16:13 GMT
I'm not keen on including the debugger in the dosbox package, and other distros do not package it either. There is a dosbox-debug package in the AUR, please use that instead.

Loading...