mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1640] valgrind not working inside firejail #1104
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1104
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sigttou on GitHub (Nov 10, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1640
Hi all,
tried to run a binary inside firejail with valgrind attached to it.
Anyone has an idea how I could get this to work? Tried white-listing ld-linux-x86-64.so.2 already.
@SkewedZeppelin commented on GitHub (Nov 10, 2017):
The default profile enables
seccomp. Firejail's default seccomp blacklist prevents the use of many debugging related syscalls. As valgrind is a debugger, without those syscalls it is useless.What you can do is the following
then
firejail valgrind [binary]optionally run
sudo firecfgto enable that profile by default so you don't need to prependfirejaileverytime.Optionally you can further refine that profile and create a pull request to upstream it for everyone else.
@smitsohu commented on GitHub (Nov 10, 2017):
Would it work with
seccomp @default, excluding only the two syscallsptraceandprocess_vm_readv?@sigttou commented on GitHub (Nov 10, 2017):
@SpotComms tried that, but keeps giving me the same error.
Even when I use
--noprofileit gives me the same errorAs soon as I figure it out I will create a pull request.
@netblue30 commented on GitHub (Nov 10, 2017):
on simple programs just a --allow-debuggers should work:
@sigttou commented on GitHub (Nov 10, 2017):
Thanks, that resolved the issue for me.
Should have read the man page more carefully there.