38 lines
1.2 KiB
Markdown
38 lines
1.2 KiB
Markdown
# Debug Code Issues
|
|
|
|
Debug the following code issues: $ARGUMENTS
|
|
|
|
## Debugging Protocol:
|
|
1. **Issue Understanding**: Analyze the problem description and expected vs actual behavior
|
|
2. **Log Analysis**: Examine relevant log files and error messages
|
|
3. **Code Investigation**: Review related source code and recent changes
|
|
4. **Reproduction**: Attempt to reproduce the issue in a controlled environment
|
|
5. **Root Cause**: Identify the underlying cause and contributing factors
|
|
|
|
## Debugging Commands:
|
|
```bash
|
|
# For Go backend
|
|
go run -race ./cmd/mev-bot
|
|
LOG_LEVEL=debug ./mev-bot start
|
|
|
|
# For Solidity contracts
|
|
npx hardhat test
|
|
forge test -vvv
|
|
|
|
# For Frontend
|
|
npm run dev
|
|
npm run test:unit
|
|
```
|
|
|
|
## Investigation Areas:
|
|
- **Go Backend**: Concurrency issues, memory leaks, parsing errors
|
|
- **Solidity Contracts**: Gas issues, reentrancy, overflow/underflow
|
|
- **Frontend**: Vue component issues, state management, web3 integration
|
|
- **Integration**: API communication, contract interactions, data flow
|
|
|
|
## Output Requirements:
|
|
- Clear problem identification with code references
|
|
- Step-by-step reproduction instructions
|
|
- Root cause analysis with technical details
|
|
- Proposed solution with implementation steps
|
|
- Test plan to verify the fix |