Ghidra1
Ghidra1
> is there a way to disable packing types by default? @Schala , I believe packing is disabled by default for structures when instantiated. Although, the C-parser always enables packing...
> same error > > ``` > Address Overflow in add: .debug_frame.13::0000006b 0x1 > ghidra.program.model.address.AddressOutOfBoundsException: Address Overflow in add: .debug_frame.13::0000006b 0x1 > at ghidra.program.model.address.AbstractAddressSpace.add(AbstractAddressSpace.java:431) > at ghidra.program.model.address.OverlayAddressSpace.add(OverlayAddressSpace.java:18) > at ghidra.program.model.address.GenericAddress.add(GenericAddress.java:237)...
The composite implementation and associated editor are not designed to scale to this number of components and certainly does not perform well when a very large number of components exist...
In addition to the composite performance, the `BitFieldEditorPanel` and `BitFieldPlacementComponent` need to be refactored to adopt some additional scaling to handle extremely large structures. In the absence of scaling, limits...
That seems rather excessive and is likely abusing the intention of reuseable "named" calling conventions. I assume this is being done to customize storage on a function-by-function basis or do...
For taylored situations as you describe (e.g., pure assembly code) we are evaluating an approach which would allow a function-specific tayloring of affected/unaffected registers, etc.. We are also evaluating similar...
I have corrected the `ProjectFileManager.dispose()` method issue which I believe is masking another exception during instantiation. Hopefully this will get pushed out within the next few days afterwhich you can...
There a lot of potential pitfalls with simply switching project-owner in prp file file due to OS/filesystem file ownership issues. The default umask on Linux and the resulting file permissions...
> * have auto analysis detect and automatically mark instructions as "split" Do to the frequent occurance of bad offcut flows we are currently not considering any generalized attempt at...
FYI - We have bumped `bsim` MAXMEM to 2GB for next release