Skip to content

scripts: add debug build to fuzz.sh - #9375

Closed
cujomalainey wants to merge 1 commit into
thesofproject:mainfrom
cujomalainey:dbg
Closed

cujomalainey wants to merge 1 commit into
thesofproject:mainfrom
cujomalainey:dbg

Conversation

@cujomalainey

Copy link
Copy Markdown
Contributor

Add flag for adding symbols in easily.

Add flag for adding symbols in easily.

Signed-off-by: Curtis Malainey <cujomalainey@chromium.org>
Comment thread scripts/fuzz.sh
Comment thread scripts/fuzz.sh
-j n Number of concurrent -jobs=n. Defaults to 1.
The value 0 uses the output of the 'nproc' command.
-d Add debug optimizations and symbols to the build.
Useful for testcase reproduction.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not add these CONFIG_DEBUG* always? Are they slowing anything down?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was my thought that it would reduce the exec/s of the fuzzer. The build already has enough to get a stack trace so I didnt think it needed anymore since the automated tools don't do anything more.

@marc-hb marc-hb left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This and #9343 made me realize we have a bit of a .config mess which I just described in brand new:

Please let me first clean-up this fuzz.sh script a little bit more accordingly. I will try to submit something tonight.

@marc-hb

marc-hb commented Aug 22, 2024

Copy link
Copy Markdown
Collaborator

I will try to submit something tonight.

Done, submitted #9389.

This moves all CONFIG_ values to .conf files which will help re-use and reduce duplicate/diverge.

Based on it, could this new -d option include the already existing app/debug_overlay.conf file?

@cujomalainey

Copy link
Copy Markdown
Contributor Author

I will try to submit something tonight.

Done, submitted #9389.

This moves all CONFIG_ values to .conf files which will help re-use and reduce duplicate/diverge.

Based on it, could this new -d option include the already existing app/debug_overlay.conf file?

That will be helpful also for enabling multiple sanitizers again. Much appreciated.

Comment thread scripts/fuzz.sh
-DCONFIG_ASAN=y
)

local debug_configs=(

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's pretty amazing that this does NOT git conflict considering I removed the entire fuzz_configs variable above (and more) in merged commit 577c9ae and replaced it with local conf_files_list=... which looks entirely different! Yet neither git cherry-pick nor git merge seem to bother - wow!

Even if not a git conflict, this is still very much a logical conflict so this PR should not be merged as is right now.

There will likely be another conflict with incoming #9409, so maybe wait for that to be merged too.

@marc-hb
marc-hb marked this pull request as draft August 30, 2024 00:05
@marc-hb
marc-hb dismissed their stale review August 30, 2024 00:05

unmergeable but git does not know

@lgirdwood

Copy link
Copy Markdown
Member

@cujomalainey still needed ?

@cujomalainey

Copy link
Copy Markdown
Contributor Author

@cujomalainey still needed ?

Yes but in a different form. We have symbols already. They just only work with lldb. I need to add a flag to switch to -Og from -O2.

@cujomalainey

Copy link
Copy Markdown
Contributor Author

Closing as I think this isn't needed anymore

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