Source Activity

Syndicate content
Haiku's main repository
Updated: 24 min 36 sec ago

FreeBSD compat: Align allocations according to FreeBSD man page.

Sat, 2016-12-10 21:58
According to the FreeBSD kernel malloc man page the allocator is expected to return power of two aligned addresses for allocations up to one page size. While it also states that this shouldn't be relied upon, at least our (directly copied) bus_dmamem_alloc expects it and drivers may depend on it as well. Looking through the FreeBSD commit logs, this expectation seems to be rooted quite deeply. This fixes watchdog timeouts in the ipro1000 driver under KVM and may help with #11953. It might also be related to #9099 and #9601 as those seem memory allocation related as well. According to the FreeBSD kernel malloc man page the allocator is expected to return power of two aligned addresses for allocations up to one page size. While it also states that this shouldn't be relied upon, at least our (directly copied) bus_dmamem_alloc expects it and drivers may depend on it as well. Looking through the FreeBSD commit logs, this expectation seems to be rooted quite deeply. This fixes watchdog timeouts in the ipro1000 driver under KVM and may help with #11953. It might also be related to #9099 and #9601 as those seem memory allocation related as well.
Categories: Development

Revert "repo rework: Re-add compatibility url field"

Sat, 2016-12-10 11:51
Revert "repo rework: Remove stubs; Breaks repo compat." Revert "repo rework: Remove need for repos to be self-aware" This reverts commit a2b2f4d6427914cdcdb59943dd8e4a0bfdcd53ee. This reverts commit 602076ef82647a48fd10f4d1ec830bb4242f9eb6. This reverts commit 5ffaf72c8a74a7eb6827e4d2b1f47c9360ddaefe. These changes break the build on Haiku and the ability to create repo mirrors, for the lack of a replacement for the URL (an UUID was evoked on the mailing lists, but not implemented). We are due for a release soon, please don't break the build. Revert "repo rework: Remove stubs; Breaks repo compat." Revert "repo rework: Remove need for repos to be self-aware" This reverts commit a2b2f4d6427914cdcdb59943dd8e4a0bfdcd53ee. This reverts commit 602076ef82647a48fd10f4d1ec830bb4242f9eb6. This reverts commit 5ffaf72c8a74a7eb6827e4d2b1f47c9360ddaefe. These changes break the build on Haiku and the ability to create repo mirrors, for the lack of a replacement for the URL (an UUID was evoked on the mailing lists, but not implemented). We are due for a release soon, please don't break the build.
Categories: Development

Revert BNode changes resulting in non bootable system

Sat, 2016-12-10 08:57
Revert "BNode: CID 602323 explicitly ignore fCStatus return value in ctor" Revert "BNode: Set fCStatus in SetTo() explicitly" Revert "BNode: Style fixes, see below for details" This reverts commit ede463195dee8536628c54ee6a4a888c0683a83f. This reverts commit 6e3445098abd1d1e4cca69ba2d959fe74fe2cb1b. This reverts commit 89c0b71c9a5acdbdb4543f025f64937bfbd893e3. We are due for a release soon. Please keep things working. Revert "BNode: CID 602323 explicitly ignore fCStatus return value in ctor" Revert "BNode: Set fCStatus in SetTo() explicitly" Revert "BNode: Style fixes, see below for details" This reverts commit ede463195dee8536628c54ee6a4a888c0683a83f. This reverts commit 6e3445098abd1d1e4cca69ba2d959fe74fe2cb1b. This reverts commit 89c0b71c9a5acdbdb4543f025f64937bfbd893e3. We are due for a release soon. Please keep things working.
Categories: Development

Debugger: Rework parts of report generation.

Sat, 2016-12-10 03:57
Team: - Adjust report generation event to include a final status code for listeners. CliContext,TeamWindow,ReportUserinterface: - Use aforementioned status code to indicate whether report generation succeeded or failed. DebugReportGenerator: - Notify listeners if report generation fails. This may have previously been responsible for some bug reports where it was indicated that the debugger hung without exiting after being asked to save a report from a crashed app. - When dumping disassembly, retrieve it directly if necessary rather than requesting it via the user interface listener. This also fixes the quirk that requesting to save a crash report while looking at the source code of a function would trigger switching it to disassembly visually. - When walking the list of threads to dump, acquire references to all of them before starting. Otherwise, it was potentially possible for a running but not crashed thread to exit while we were generating the report, leaving us with a pointer to a deleted thread. This was most likely the cause of one of the crashes reported in #13082. - When receiving the notification that source code state has changed, clear the waiting function. Otherwise, it was potentially possible for us to get other state change notifications, leading to the data semaphore being released too often. This would then cause later potential waits such as the stack frame memory dump to not actually wait when they should, potentially leading them to dereference objects that weren't yet ready. This fixes another of the crashes in #13802. Team: - Adjust report generation event to include a final status code for listeners. CliContext,TeamWindow,ReportUserinterface: - Use aforementioned status code to indicate whether report generation succeeded or failed. DebugReportGenerator: - Notify listeners if report generation fails. This may have previously been responsible for some bug reports where it was indicated that the debugger hung without exiting after being asked to save a report from a crashed app. - When dumping disassembly, retrieve it directly if necessary rather than requesting it via the user interface listener. This also fixes the quirk that requesting to save a crash report while looking at the source code of a function would trigger switching it to disassembly visually. - When walking the list of threads to dump, acquire references to all of them before starting. Otherwise, it was potentially possible for a running but not crashed thread to exit while we were generating the report, leaving us with a pointer to a deleted thread. This was most likely the cause of one of the crashes reported in #13082. - When receiving the notification that source code state has changed, clear the waiting function. Otherwise, it was potentially possible for us to get other state change notifications, leading to the data semaphore being released too often. This would then cause later potential waits such as the stack frame memory dump to not actually wait when they should, potentially leading them to dereference objects that weren't yet ready. This fixes another of the crashes in #13802.
Categories: Development

Add SoftwareUpdater to regular image

Fri, 2016-12-09 21:52
Categories: Development

SoftwareUpdater: Swap cancel and default buttons so default is rightmost

Fri, 2016-12-09 21:52
... and add default horizontal space between text and buttons ... and add default horizontal space between text and buttons
Categories: Development

SoftwareUpdater: Replace %d with B_PRIu32 for uint32

Fri, 2016-12-09 21:50
(gcc2h build gave me a stern warning) (gcc2h build gave me a stern warning)
Categories: Development

SoftwareUpdater: Add some details on what's available

Thu, 2016-12-08 23:38
* Just example text for now to be filled in with data from our package kit. * Just example text for now to be filled in with data from our package kit.
Categories: Development

SoftwareUpdater: Initial work on a GUI software updater

Thu, 2016-12-08 18:43
* Planning on having a notification box when updates available. * Clicking the notification box will pop up the SoftwareUpdater with a simple "Apply Updates" button * Currently users need to know to 'pkgman update' * Planning on having a notification box when updates available. * Clicking the notification box will pop up the SoftwareUpdater with a simple "Apply Updates" button * Currently users need to know to 'pkgman update'
Categories: Development

MediaEventLooper: Remove soft real time lateness bounding

Thu, 2016-12-08 15:08
* The media_kit isn't an hard real time beast. Bounding lateness looked like the perfect way to enable reasonable soft real time performance and thus limiting port writes and reads between producers and consumers. It seems to don't work very well so I just remove it. * The result of the recent code simplification makes it equal to my first version, before any discussion on it happened. * Thanks to AlienSoldier for testing such issues. * Fixes #13069. * The media_kit isn't an hard real time beast. Bounding lateness looked like the perfect way to enable reasonable soft real time performance and thus limiting port writes and reads between producers and consumers. It seems to don't work very well so I just remove it. * The result of the recent code simplification makes it equal to my first version, before any discussion on it happened. * Thanks to AlienSoldier for testing such issues. * Fixes #13069.
Categories: Development

repo rework: Re-add compatibility url field

Thu, 2016-12-08 13:57
* We saw 3rd party repos break as well oddly. * Reintroduces the url field in a little bit cleaner way. * Should solve "Failed to open repository file" errors * Once everyone updates beyond hrev50723 this is no longer needed. * We saw 3rd party repos break as well oddly. * Reintroduces the url field in a little bit cleaner way. * Should solve "Failed to open repository file" errors * Once everyone updates beyond hrev50723 this is no longer needed.
Categories: Development

Debugger: Adjustments to report generator.

Thu, 2016-12-08 04:55
DebugReportGenerator: - Due to the changes made with respect to correctly handling switching to disassembly explicitly, the report generator needs to request loading source files as it walks the stack trace in order to get source-based line number information. Fixes crash reports having -1 as the line number in cases where debug information was available, but the user hadn't yet looked at the source file in question. LoadSourceCodeJob: - Cleanup. DebugReportGenerator: - Due to the changes made with respect to correctly handling switching to disassembly explicitly, the report generator needs to request loading source files as it walks the stack trace in order to get source-based line number information. Fixes crash reports having -1 as the line number in cases where debug information was available, but the user hadn't yet looked at the source file in question. LoadSourceCodeJob: - Cleanup.
Categories: Development

Update usb.ids from www.linux-usb.org

Thu, 2016-12-08 04:20
Categories: Development

repo rework: Remove stubs; Breaks repo compat.

Thu, 2016-12-08 03:27
* These stubbs satisfied older Haiku releases that required the URL * Users running nightly images will need to upgrade to hrev50723 - hrev50744 before upgrading further * Getting this out of the way now before the beta comes out. * New installations shouldn't suffer any problems. * These stubbs satisfied older Haiku releases that required the URL * Users running nightly images will need to upgrade to hrev50723 - hrev50744 before upgrading further * Getting this out of the way now before the beta comes out. * New installations shouldn't suffer any problems.
Categories: Development

libdebugger: Fix a regression with ELF loading in some cases.

Thu, 2016-12-08 03:12
ElfFile: - The refactoring in commit 2c50fbb8e16102886d0cd28135dae0b58b9d33f4 inadvertently introduced a failure case if a section in the ELF file is skipped, since it was explicitly passing in the insertion index to BObjectList::AddItem(). Since in the skipped case, this would be out of bounds for the list's current size, this would cause the whole operation to fail with an out of memory error, and consequently halt all further loading of debug information for that particular file. This manifested itself with libroot on at least gcc5, where no symbols could be seen. ElfFile: - The refactoring in commit 2c50fbb8e16102886d0cd28135dae0b58b9d33f4 inadvertently introduced a failure case if a section in the ELF file is skipped, since it was explicitly passing in the insertion index to BObjectList::AddItem(). Since in the skipped case, this would be out of bounds for the list's current size, this would cause the whole operation to fail with an out of memory error, and consequently halt all further loading of debug information for that particular file. This manifested itself with libroot on at least gcc5, where no symbols could be seen.
Categories: Development