Skip to content

Conversation

gsingh93
Copy link

@gsingh93 gsingh93 commented Jul 25, 2018

Sometimes the program counter points to a non-readable memory address after a crash. When we run the gdb_cmds.txt file in funfuzz, commands like x/8i $pc will fail. I'm not sure if this is the right solution, but I just check for the text 'Error in sourced command file' in the crashInstruction variable and set the instruction to None so it's ignored. I tested this locally and it seems to work.

Fixes #496.

@codecov-io
Copy link

codecov-io commented Jul 25, 2018

Codecov Report

Merging #497 into master will decrease coverage by <.01%.
The diff coverage is 50%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #497      +/-   ##
==========================================
- Coverage   77.93%   77.93%   -0.01%     
==========================================
  Files         126      126              
  Lines       11979    11981       +2     
==========================================
+ Hits         9336     9337       +1     
- Misses       2643     2644       +1
Impacted Files Coverage Δ
FTB/Signatures/CrashInfo.py 90.36% <50%> (-0.09%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 50aad0e...0640091. Read the comment docs.

@gsingh93
Copy link
Author

@choller thoughts on this?

@gsingh93
Copy link
Author

gsingh93 commented Aug 4, 2018

ping @choller

@nth10sd
Copy link
Contributor

nth10sd commented Nov 7, 2018

@jschwartzentruber may probably be a better person for now?

@jschwartzentruber
Copy link
Contributor

@gsingh93 Thanks for fixing this. Do you have an example log so we can add a test? I worry that Error in sourced command file is too non-specific. Is that all we get from GDB?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants