- --- In firstname.lastname@example.org, Gerhard Postpischil <gerhardp@...> wrote:
>Not sure what that's all about, but regardless, I
> kerravon86 wrote:
> > It appears that the diff only shows regions that have
> > had changes. Here is the full code:
> It's too pretty to be a diff <g>
found out in the original link that you can click
on "long coloured diff" in the bottom left and it
shows more of the code, including the bit you queried.
So what are your thoughts on an option in DISASM
to make the DS say X'00000' instead of X'12345..'?
Here's the procedure required because of that:
(these two steps are required because the disassembler doesn't
generate DS X'00' and instead generates DS X'12...')
Run disasm on real executable into temporary dataset, using
storage (DS) markers
Run assemble on it again, and link a temporary executable
(end of annoying steps)
Run disasm on it again, storing result into AUTOASM.STORLIST
- On 2/14/2010 5:20 AM, kerravon86 wrote:
> disbug.zip is available in the files section.I'm done with it. I reorganized the way the DATATYPE field is
populated, and got this to work better than I expected.
The 136, and related DATA splitting, is also fixed, hopefully
permanently. I completely tossed the old code and replaced it by
something easier to follow.
I thought the last version had the FILLER object field = 0 fix,
but it misbehaved during tests. I have a fix that will go in
tomorrow for testing.
I briefly looked at the length vs. end address, and can't find
anything obvious - all the code appear to be correct.
I still need to work on object card processing; there are
problems with the entry point, the ENTRY statement, and
identifying CSECT types correctly.
> Be sure to check out the description in the files area. :-)Couldn't find one <g>