Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically label known contract addresses in traces #7530

Open
2 tasks done
zhiqiangxu opened this issue Mar 31, 2024 · 1 comment · May be fixed by #7544
Open
2 tasks done

Automatically label known contract addresses in traces #7530

zhiqiangxu opened this issue Mar 31, 2024 · 1 comment · May be fixed by #7544
Labels
T-bug Type: bug

Comments

@zhiqiangxu
Copy link

zhiqiangxu commented Mar 31, 2024

Component

Forge

Have you ensured that all of these are up to date?

  • Foundry
  • Foundryup

What version of Foundry are you on?

forge 0.2.0 (7922fd5 2024-02-05T00:19:20.258041000Z)

What command(s) is the bug in?

forge test

Operating System

macOS (Intel)

Describe the bug

This issue is a follow-up issue of this one, but since that one is old, I'd like to issue a new one.

It seems 0x0000000000000000000000000000000000000001 is a contract automatically created by foundry, but not labeled in traces:

[0] 0x0000000000000000000000000000000000000001::fallback{value: 1000000000000000000}()

It can be reproduced here by running forge test --mp test/BatchInbox.t.sol -vvv

@zhiqiangxu zhiqiangxu added the T-bug Type: bug label Mar 31, 2024
@grandizzy
Copy link
Collaborator

grandizzy commented Apr 1, 2024

here's the list of precompiles, probably can be labeled with Forge-{Name} for clarity? https://book.getfoundry.sh/misc/precompile-registry

@grandizzy grandizzy linked a pull request Apr 2, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-bug Type: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants