[jira] [Assigned] (DAFFODIL-2173) Data dumps should be bit-aware

2019-07-01 Thread Olabusayo Kilo (JIRA)


 [ 
https://issues.apache.org/jira/browse/DAFFODIL-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olabusayo Kilo reassigned DAFFODIL-2173:


Assignee: Olabusayo Kilo

> Data dumps should be bit-aware
> --
>
> Key: DAFFODIL-2173
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2173
> Project: Daffodil
>  Issue Type: Bug
>  Components: Debugger
>Affects Versions: 2.4.0
>Reporter: Olabusayo Kilo
>Assignee: Olabusayo Kilo
>Priority: Major
>
> Data dumps print out bytes without regard to the bit offset. So if some bits 
> have already been consumed, the dumps might include those already consumed 
> bits.
> Ideally we would like to be bit sensitive. A possible solution would be to 
> track if the first byte of the left over data, already had consumed bytes i.e 
> ended mid-byte, and only display those non consumed bits. That is, if the 
> data ended at bit 5, and bit order is mostSignificantBitFirst, then this 
> picture would look like x000 (where the 0's are the actual left over data 
> bits in that first byte of the left over data.) If bitOrder is 
> leastSignificantBitFirst the picture would look like 000x.
> inStream.fillByteArray takes the bit offset into accound and can be utilized.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DAFFODIL-2173) Data dumps should be bit-aware

2019-06-28 Thread Olabusayo Kilo (JIRA)


 [ 
https://issues.apache.org/jira/browse/DAFFODIL-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olabusayo Kilo reassigned DAFFODIL-2173:


Assignee: (was: Olabusayo Kilo)

> Data dumps should be bit-aware
> --
>
> Key: DAFFODIL-2173
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2173
> Project: Daffodil
>  Issue Type: Bug
>  Components: Debugger
>Affects Versions: 2.4.0
>Reporter: Olabusayo Kilo
>Priority: Major
>
> Data dumps print out bytes without regard to the bit offset. So if some bits 
> have already been consumed, the dumps might include those already consumed 
> bits.
> Ideally we would like to be bit sensitive. A possible solution would be to 
> track if the first byte of the left over data, already had consumed bytes i.e 
> ended mid-byte, and only display those non consumed bits. That is, if the 
> data ended at bit 5, and bit order is mostSignificantBitFirst, then this 
> picture would look like x000 (where the 0's are the actual left over data 
> bits in that first byte of the left over data.) If bitOrder is 
> leastSignificantBitFirst the picture would look like 000x.
> inStream.fillByteArray takes the bit offset into accound and can be utilized.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DAFFODIL-2173) Data dumps should be bit-aware

2019-06-28 Thread Olabusayo Kilo (JIRA)


 [ 
https://issues.apache.org/jira/browse/DAFFODIL-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olabusayo Kilo reassigned DAFFODIL-2173:


Assignee: Olabusayo Kilo

> Data dumps should be bit-aware
> --
>
> Key: DAFFODIL-2173
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2173
> Project: Daffodil
>  Issue Type: Bug
>  Components: Debugger
>Affects Versions: 2.4.0
>Reporter: Olabusayo Kilo
>Assignee: Olabusayo Kilo
>Priority: Major
>
> Data dumps print out bytes without regard to the bit offset. So if some bits 
> have already been consumed, the dumps might include those already consumed 
> bits.
> Ideally we would like to be bit sensitive. A possible solution would be to 
> track if the first byte of the left over data, already had consumed bytes i.e 
> ended mid-byte, and only display those non consumed bits. That is, if the 
> data ended at bit 5, and bit order is mostSignificantBitFirst, then this 
> picture would look like x000 (where the 0's are the actual left over data 
> bits in that first byte of the left over data.) If bitOrder is 
> leastSignificantBitFirst the picture would look like 000x.
> inStream.fillByteArray takes the bit offset into accound and can be utilized.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)