Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

Consider adding solc assembler output in /build #1246

Open
rocky opened this issue Aug 31, 2018 · 9 comments
Open

Consider adding solc assembler output in /build #1246

rocky opened this issue Aug 31, 2018 · 9 comments
Assignees
Labels

Comments

@rocky
Copy link

rocky commented Aug 31, 2018

  • [x ] I've asked for help in the Truffle Gitter before filing this issue.

Issue

For various analysis tools it may be helpful to look at the assembler output of solc. Could this be done as a configuration switch, if not always?

I also note that -asm seems to give more information than -asm-json, but asm-json has interesting detail on its own.

@eggplantzzz eggplantzzz self-assigned this Sep 24, 2018
@stale
Copy link

stale bot commented Nov 23, 2018

Thank you for raising this issue! It has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you would like to keep this issue open, please respond with information about the current state of this problem.

@stale stale bot added the stale label Nov 23, 2018
@eggplantzzz
Copy link
Contributor

Not stale

@stale
Copy link

stale bot commented Nov 26, 2018

Thanks for your response! This issue is no longer considered stale and someone from the Truffle team will try to respond as soon as they can.

@stale stale bot removed the stale label Nov 26, 2018
@rocky
Copy link
Author

rocky commented Nov 26, 2018

Actually, I think this is part of a bigger discussion of what should go into the the build/contracts JSON, and library routines involved there.

I don't think solving this as an independant thing is as important as the discussion of what should go in there.

I am hoping that by working with folks in integrating Mythril into the currently developing plugin architecture we can resolve this as well as other things.

@stale
Copy link

stale bot commented Jan 25, 2019

Thank you for raising this issue! It has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you would like to keep this issue open, please respond with information about the current state of this problem.

@stale stale bot added the stale label Jan 25, 2019
@gnidan
Copy link
Contributor

gnidan commented Jan 25, 2019

not stale

@stale
Copy link

stale bot commented Jan 25, 2019

Thanks for your response! This issue is no longer considered stale and someone from the Truffle team will try to respond as soon as they can.

@stale stale bot removed the stale label Jan 25, 2019
@rocky
Copy link
Author

rocky commented Jan 25, 2019

Is this related to this and indirectly #1645 ?

@gnidan
Copy link
Contributor

gnidan commented Dec 4, 2019

Could be related to the stuff in artifact-updates, but I think it's separate from #1645.

The work here is just adding to the artifacts. Should be fine.

@haltman-at haltman-at added the needs requirements feature request is unclear label Nov 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants