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

Add option to dump core with gdb after a program signals unexpectedly #27

Open
ngie-eign opened this issue Jan 2, 2017 · 1 comment

Comments

@ngie-eign
Copy link
Contributor

ngie-eign commented Jan 2, 2017

I had to manually execute an ATF test program in a loop with gdb in order reproduce the issue noted in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215715 . I shouldn't have to do this -- the framework should do this for me.

$ cat cond_timedwait_race.gdbscript
set args cond_timedwait_race
run
generate-core-file
$ while gdb -batch -x cond_timedwait_race.gdbscript /usr/tests/lib/libthr/cond_test cond_timedwait_race; do :; done
@jmmv
Copy link
Member

jmmv commented Jan 11, 2017

I don't understand what you mean by "dump core with gdb" (the gdb part). Dumping core should happen regardless of gdb on reception of certain signals.

What I had in mind a long time ago to do in this area, which I think would resolve your situation, was to add an option to both kyua test and kyua debug to keep the work directories around for any failed tests. Those directories would then contain the core dumps you are interested in.

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

No branches or pull requests

2 participants