--core-file doesn't work as intended
Bug #397023 reported by
Trond Norbye
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Fix Released
|
Low
|
Trond Norbye |
Bug Description
If you start drizzled with --core-file you would expect it to write a corefile if it crash, but this really doesn't happen. All it does is that it sets the RLIM_CORE to unlimited.
The problem is the test where it determines if it should trap the signals or not:
if (!(test_flags & TEST_NO_STACKTRACE) || (test_flags & TEST_CORE_
If you look closely to this test you will see that it will only evaluate to false if TEST_NO_STACKTRACE is set, and TEST_CORE_ON_SIGNAL is false.
The correct test would be:
if (!(test_flags & TEST_NO_STACKTRACE || test_flags & TEST_CORE_
This evaluated to false if TEST_NO_STACKTRACE or TEST_CORE_ON_SIGNAL is set.
Related branches
lp:~trond-norbye/drizzle/bug_397023
- Monty Taylor: Approve
- Jay Pipes (community): Approve
- Diff: None lines
Changed in drizzle: | |
assignee: | nobody → Trond Norbye (trond-norbye) |
status: | New → Fix Committed |
Changed in drizzle: | |
importance: | Undecided → Low |
milestone: | none → aloha |
status: | Fix Committed → Fix Released |
To post a comment you must log in.