Development

btreeTest: Fix build with gcc2.

Source Activity - Wed, 2014-10-29 22:47
Categories: Development

Fix build of intel partitioning add-on by building its own MBR.

Source Activity - Wed, 2014-10-29 22:25
It previously shared the same generated MBR header with bin/writembr, but they have incompatible needs. The intel partitioning add-on only wants the MBR code, while writembr wants the whole sector. Build the desired version of the MBR separately for each target instead of sharing a single header. It previously shared the same generated MBR header with bin/writembr, but they have incompatible needs. The intel partitioning add-on only wants the MBR code, while writembr wants the whole sector. Build the desired version of the MBR separately for each target instead of sharing a single header.
Categories: Development

Avoid space after -include.

Source Activity - Wed, 2014-10-29 22:17
This seems to make cpp unhappy. Note that other fixes seems to be needed to get the build running with gcc2 (missing includes and the like.) This seems to make cpp unhappy. Note that other fixes seems to be needed to get the build running with gcc2 (missing includes and the like.)
Categories: Development

Re-enable raw audio ffmpeg output.

Source Activity - Wed, 2014-10-29 21:47
Categories: Development

Ticket #9712 (Add support for expression evaluation) closed

Latest Bugs & Tasks - Wed, 2014-10-29 21:42
fixed:

Implemented with some caveats in hrev48153.

Categories: Development

writembr: Fix too short MBR due to wrong compile flags.

Source Activity - Wed, 2014-10-29 21:38
The compile flags were set so that only the boot code itself would be produced, excluding the (dummy) partition table and signature. The code in writembr still assumed that the MBR would be 512 bytes however and therefore access the data array out of bounds. Fix flags to produce the full 512 byte MBR sector and add a STATIC_ASSERT so that the size assumption is checked on compilation. Also fix a typo in mbr.nasm, mostly to trigger re-generation of the MBR data that one would otherwise need to remove manually... The two out of bounds array accesses were pointed out by CID 1249923 and CID 1249924, the insufficiently large target buffer of the memcpy by CID 1249901. The compile flags were set so that only the boot code itself would be produced, excluding the (dummy) partition table and signature. The code in writembr still assumed that the MBR would be 512 bytes however and therefore access the data array out of bounds. Fix flags to produce the full 512 byte MBR sector and add a STATIC_ASSERT so that the size assumption is checked on compilation. Also fix a typo in mbr.nasm, mostly to trigger re-generation of the MBR data that one would otherwise need to remove manually... The two out of bounds array accesses were pointed out by CID 1249923 and CID 1249924, the insufficiently large target buffer of the memcpy by CID 1249901.
Categories: Development

Debugger: Implement expression variable value resolution.

Source Activity - Wed, 2014-10-29 21:32
General: - Resolving variable values requires both a stack frame and a CPU state. Adjust all interfaces and callers accordingly. ExpressionEvaluationJob: - Pass additional parameters needed for variable value resolution. - If variable resolution is desired, ExpressionEvaluationJob now creates a temporary ValueNodeManager for that purpose. - If the expression parser returns a value node pointer that needs to be resolved, schedule a corresponding job and wait. CLanguageExpressionEvaluator: - Clean up some leftovers that were preventing variable names from being handled properly in some cases. - Implement handling of identifier names. These are now looked up against the value node graph of the active node manager, and if found, corresponding values are retrieved. If the value has not yet been resolved, an exception is thrown to ask that to be done. This gets value resolution working for basic local variables and function parameters, and consequently, #9712. Structure/class members and/or pointer indirection aren't yet handled. General: - Resolving variable values requires both a stack frame and a CPU state. Adjust all interfaces and callers accordingly. ExpressionEvaluationJob: - Pass additional parameters needed for variable value resolution. - If variable resolution is desired, ExpressionEvaluationJob now creates a temporary ValueNodeManager for that purpose. - If the expression parser returns a value node pointer that needs to be resolved, schedule a corresponding job and wait. CLanguageExpressionEvaluator: - Clean up some leftovers that were preventing variable names from being handled properly in some cases. - Implement handling of identifier names. These are now looked up against the value node graph of the active node manager, and if found, corresponding values are retrieved. If the value has not yet been resolved, an exception is thrown to ask that to be done. This gets value resolution working for basic local variables and function parameters, and consequently, #9712. Structure/class members and/or pointer indirection aren't yet handled.
Categories: Development

NetworkSetup: move renegociate and disable buttons to HardwareView

Source Activity - Wed, 2014-10-29 21:15
The idea is making the interface list a generic list to add some stuff that are not interfaces there (ie services: DNS, FTP, SSH, ...) The idea is making the interface list a generic list to add some stuff that are not interfaces there (ie services: DNS, FTP, SSH, ...)
Categories: Development

Ticket #11328 ([packagefs] Killed (by death)) closed

Latest Bugs & Tasks - Wed, 2014-10-29 20:07
fixed:

Should be fixed (at least for now) in hrev48151.

Categories: Development

Increase the size of the kernel FD table

Source Activity - Wed, 2014-10-29 20:06
With packagefs potentially opening quite a few packages the default of 256 slots is a bit tight. It's 4096 now, which should be safe for a while, but we might want to consider resizing the table dynamically and probably even switching to another algorithm for allocating the slots. Should fix #11328. With packagefs potentially opening quite a few packages the default of 256 slots is a bit tight. It's 4096 now, which should be safe for a while, but we might want to consider resizing the table dynamically and probably even switching to another algorithm for allocating the slots. Should fix #11328.
Categories: Development

Make vfs_resize_fd_table() accessible in the kernel

Source Activity - Wed, 2014-10-29 20:01
Also update some types from int to uint32. Also update some types from int to uint32.
Categories: Development

Ticket #9808 (NetSurf crashes on Haiku R1A4.1 (gcc2hybrid)) closed

Latest Bugs & Tasks - Wed, 2014-10-29 18:49
fixed:

NetSurf currently available in package repos works.

Categories: Development

[haiku-development] [RFC] kernel_args tweaks (was: [haiku-commits] haiku: hrev48117) (François Revol)

Development mailing list - Wed, 2014-10-29 18:45
On 27/10/2014 10:57, ingo_weinhold@xxxxxx wrote: fa80e7b: x86 kernel args: Increase number of page tables While we are at it, there are a few things about kernel_args that would need to be addressed : - the framebuffer description only gives the depth, but doesn't say anything about the format. On x86 this isn't so much of a problem, but ...
Categories: Development

[haiku-development] Re: [RFC] seek(SEEK_END) on block devices (Axel Dörfler)

Development mailing list - Wed, 2014-10-29 18:45
Am 28.10.2014 15:32, schrieb François Revol: On 28/10/2014 15:01, François Revol wrote: It seems like some programs now use lseek(SEEK_END) to determine block devices size, instead of non-portable ioctls() like BLKGETSIZE64. [...] ...
Categories: Development

[haiku-development] Re: [RFC] seek(SEEK_END) on block devices (François Revol)

Development mailing list - Wed, 2014-10-29 18:45
On 28/10/2014 15:01, François Revol wrote: It seems like some programs now use lseek(SEEK_END) to determine block devices size, instead of non-portable ioctls() like BLKGETSIZE64. One such program is ddrescue. I'm wondering about adding support for it in the vfs. The POSIX specs are not really verbose on this, they don't really make it mandatory explicitely nor forbid it: ...
Categories: Development

[haiku-development] [RFC] seek(SEEK_END) on block devices (François Revol)

Development mailing list - Wed, 2014-10-29 18:45
It seems like some programs now use lseek(SEEK_END) to determine block devices size, instead of non-portable ioctls() like BLKGETSIZE64. One such program is ddrescue. I'm wondering about adding support for it in the vfs. The POSIX specs are not really verbose on this, they don't really make it mandatory explicitely nor forbid it: ...
Categories: Development

[haiku-development] Re: Google Code-In 2014 (Augustin Cavalier)

Development mailing list - Wed, 2014-10-29 18:45
On 10/28/2014 02:16 AM, scottmc wrote: Note that some or all of these may or may not end up in our final list to be entered into Melange. This is just to gather possible task ideas. We like to have 200+ tasks loaded up and ready to go by the start of the contest which is Dec 1st, 2014. Also note that Qt and Java ports are working and in HaikuDepot, so you can add some tasks related to those to the list (we don't have KDElibs so no KDE apps though). ...
Categories: Development

[haiku-development] Google Code-In 2014 (scottmc)

Development mailing list - Wed, 2014-10-29 18:45
I have signed Haiku up as a possible mentoring org for Google Code-In 2014. If you would like to be a mentor for Haiku this year contact me off-list. Our brain storming ideas wiki page it here: If you have task ideas and have wiki editing permissions feel free to update the wiki page. If you have idea(s) and don't have wiki editing permissions you can still suggest ideas by filling out the form here: ...
Categories: Development

[haiku-development] Re: Contribute to Create an XFS file system driver (Richie Nyhus)

Development mailing list - Wed, 2014-10-29 18:45
Hi, The European devs are all busy with a conference held over this weekend. While you wait for them to be free you could have a look at our documentation. You will first need to install Haiku if you haven't already. If you want to build Haiku from source go here: ...
Categories: Development
Syndicate content