Use MySQL Code to get stack trace
Bug #766305 reported by
Peter Zaitsev
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Wishlist
|
Alexey Kopytov | ||
2.0 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.2 |
Fix Released
|
Wishlist
|
Alexey Kopytov |
Bug Description
Now If Xtrabackup is crashing with segmentation fault we do not know where crash happens.
We should investigate if we can use signal handler and trace library from MySQL so we can know where crash has happened this will allow us to a lot better to deal with this kind of bugs.
Related branches
lp:~akopytov/percona-xtrabackup/bug766305
- Alexey Kopytov (community): Approve
-
Diff: 250 lines (+65/-94)6 files modifiedconfigure.cmake (+2/-1)
sql/signal_handler.cc (+5/-84)
storage/innobase/include/univ.i (+3/-9)
storage/innobase/xtrabackup/src/CMakeLists.txt (+2/-0)
storage/innobase/xtrabackup/src/xtrabackup.cc (+17/-0)
storage/innobase/xtrabackup/test/t/bug766305.sh (+36/-0)
Changed in percona-xtrabackup: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PXB-101