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
segmentation fault in gbak when interrupted with Ctrl-C [CORE3150] #3527
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff Damyan, this is not related with CORE3143. Quite another problem. |
Commented by: Damyan Ivanov (dam) Sorry I didn't notice there are threads. Since I have deleted the core file from yesterday, I reproduced the segfault again and this time I got a very long backtrace, seems like an endless recursion. Here it is. I used "thread apply all bt" gdb command and ideed two threads are visible. GNU gdb (GDB) 7.2-debian Thread 2 (Thread 3457): Thread 1 (Thread 3456): |
Commented by: Damyan Ivanov (dam) Here is the multi-threaded backtrace of the original segfault, only 5 frames. No mater what debug packages I install for libstdc++ or libicu, the ???? frames stay that way. GNU gdb (GDB) 7.2-debian Thread 2 (Thread 5459): Thread 1 (Thread 5458): |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5.1 [ 10333 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Damyan Ivanov (dam)
Most of the time when I interrupt gbak with Ctrl-C while backing up, it terminates with a segmentation fault.
The problem may be related to CORE3143 (gstat segfaults when interrupted), but since the offending code seems to be in burp.cpp, I think a separate report is appropriate.
Classic, version 2.5.0.26074 (SVN revision 51557).
The command run was "gbak -v -b server:db stdout > /dev/null"
Here is the backtrace:
Program terminated with signal 11, Segmentation fault.
#0 0x0000000000426dc1 in BURP_print_status (status_vector=<value optimized out>,
flagStuff=<value optimized out>) at ../src/burp/burp.cpp:1403
1403 tdgbl->uSvc->setServiceStatus(vector);
(gdb) bt
#0 0x0000000000426dc1 in BURP_print_status (status_vector=<value optimized out>,
flagStuff=<value optimized out>) at ../src/burp/burp.cpp:1403
#1 0x000000000040558a in (anonymous namespace)::general_on_error () at ../temp/std/burp/backup.cpp:2078
#2 0x0000000000409ee5 in get_fields (relation=<value optimized out>)
at ../temp/std/burp/backup.cpp:2384
#3 (anonymous namespace)::put_relation (relation=<value optimized out>)
at ../temp/std/burp/backup.cpp:4342
#4 0x000000000040eda4 in (anonymous namespace)::write_relations () at ../temp/std/burp/backup.cpp:7254
#5 0x00000000004122e1 in BACKUP_backup (dbb_file=<value optimized out>,
file_name=<value optimized out>) at ../temp/std/burp/backup.cpp:1794
#6 0x00000000004296ff in gbak (uSvc=0x7fff3514ba68) at ../src/burp/burp.cpp:1088
#7 0x000000000042d610 in main (argc=<value optimized out>, argv=<value optimized out>)
at ../src/burp/burpMain.cpp:47
If the -v switch is dropped, the backtrace is slightly different:
Program terminated with signal 11, Segmentation fault.
#0 0x0000000000426dc1 in BURP_print_status (status_vector=<value optimized out>,
flagStuff=<value optimized out>) at ../src/burp/burp.cpp:1403
1403 tdgbl->uSvc->setServiceStatus(vector);
(gdb) bt
#0 0x0000000000426dc1 in BURP_print_status (status_vector=<value optimized out>,
flagStuff=<value optimized out>) at ../src/burp/burp.cpp:1403
#1 0x0000000000426ee0 in BURP_error_redirect (status_vector=0x7f33cab9e208, errcode=29, arg=...)
at ../src/burp/burp.cpp:1253
#2 0x00000000004104fe in (anonymous namespace)::put_data (relation=<value optimized out>)
at ../temp/std/burp/backup.cpp:3654
#3 0x000000000041268a in BACKUP_backup (dbb_file=<value optimized out>,
file_name=<value optimized out>) at ../temp/std/burp/backup.cpp:1840
#4 0x00000000004296ff in gbak (uSvc=0x7fffeca4f228) at ../src/burp/burp.cpp:1088
#5 0x000000000042d610 in main (argc=<value optimized out>, argv=<value optimized out>)
at ../src/burp/burpMain.cpp:47
Commits: 093179e
The text was updated successfully, but these errors were encountered: