Bug#1006744: open-vm-tools core dump on debian 10
Hi Bernd, We are suspecting some thing wrong with syslog, since this is the call which is failing. So Is syslog has any dependency issues or any other issue causing the syslog failure. Thanks, Girish Internal Use - Confidential -Original Message- From: Bernd Zeimetz Sent: Tuesday, March 8, 2022 7:36 PM To: Chilukuri, Girish - Dell Team; 1006...@bugs.debian.org Cc: Singh, Harmeet - Dell Team; Paturu, Santhosh - Dell Team Subject: Re: Bug#1006744: open-vm-tools core dump on debian 10 [EXTERNAL EMAIL] Hi Girish, could you give 11.3.5 from buster-backports-sloppy a try please? If that doesn't fix it, 12.0 was released recently, but that will take a bit until packages are ready. You could download it from gthub and build/test it, though. Also - please note that bullseye is the current stable release. Bernd On 2022-03-08 11:18, Chilukuri, Girish - Dell Team wrote: > Hi Bernd, >Debian buster we are using. > > Thanks, > Girish > > > Internal Use - Confidential > > -Original Message- > From: Bernd Zeimetz > Sent: Tuesday, March 8, 2022 2:13 PM > To: Chilukuri, Girish - Dell Team; 1006...@bugs.debian.org > Cc: Singh, Harmeet - Dell Team; Paturu, Santhosh - Dell Team > Subject: Re: Bug#1006744: open-vm-tools core dump on debian 10 > > > [EXTERNAL EMAIL] > > Hi, > > did you actually install the debug packages? The backtrace doesn't > look like that. > Please do so. > > https://urldefense.com/v3/__https://wiki.debian.org/HowToGetABacktrace > __;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76w > Y7MGw9htYJ8$ > [wiki[.]debian[.]org] > > Which release are you using? Bullseye? Or something else? What is > "your product"? > > > Thanks, > > Bernd > > On 2022-03-08 07:37, Chilukuri, Girish - Dell Team wrote: >> Hi Bernd, >> Below is the full backtrace from all threads from the >> core file. >> >> gdb /usr/bin/vmtoolsd rp_core.417 >> >> GNU gdb (Debian 8.2.1-2+b3) 8.2.1 >> Copyright (C) 2018 Free Software Foundation, Inc. >> License GPLv3+: GNU GPL version 3 or later >> <https://urldefense.com/v3/__http://gnu.org/licenses/gpl.html__;!!LpK >> I!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGF37 >> RWWE$ >> [gnu[.]org]> >> This is free software: you are free to change and redistribute it. >> There is NO WARRANTY, to the extent permitted by law. >> Type "show copying" and "show warranty" for details. >> This GDB was configured as "x86_64-linux-gnu". >> Type "show configuration" for configuration details. >> For bug reporting instructions, please see: >> <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/bugs/__; >> !!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7 >> MGIaDgDPE$ >> [gnu[.]org]>. >> Find the GDB manual and other documentation resources online at: >> >> <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/document >> ation/__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9p >> v-_z76wY7MGraty7eo$ >> [gnu[.]org]>. >> >> For help, type "help". >> Type "apropos word" to search for commands related to "word"... >> Reading symbols from /usr/bin/vmtoolsd...(no debugging symbols >> found)...done. >> [New LWP 417] >> [New LWP 1105] >> [Thread debugging using libthread_db enabled] Using host libthread_db >> library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1". >> Core was generated by `/usr/bin/vmtoolsd'. >> Program terminated with signal SIGSEGV, Segmentation fault. >> #0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120 >> 120 ../sysdeps/x86_64/multiarch/../strlen.S: No such file or >> directory. >> [Current thread is 1 (Thread 0x7f321f095780 (LWP 417))] >> (gdb) where >> #0 0x7f321f589206 in __strlen_sse2 () at >> ../sysdeps/x86_64/multiarch/../strlen.S:120 >> #1 0x7f321f56b475 in __GI___fputs_unlocked >> (str=0x7f321e2f7ac8 > 0x7f321e2f7ac8>, fp=fp@entry=0x55d222325690) >> at iofputs_u.c:34 >> #2 0x7f321f5e4868 in __GI___vsyslog_chk (pri=, >> flag=1, fmt=0x7f321edc083c "%s.", ap=0x7ffd36e1eda0) >> at ../misc/syslog.c:205 >> #3 0x7f321f5e4dff in __syslog_chk (pri=, >> flag=, fmt=) >> at ../misc/syslog.c:129 >> #4 0x7f321edbb1db in Audit_EventV () at /lib/libvgauth.so.0 >> #5 0x7f321edbb2a4 in Audit_Event () at /lib/libvgauth.so.0 >> #6 0x7f321edb7f95 in VGAuth_AuditEvent () a
Bug#1006744: open-vm-tools core dump on debian 10
Hi Bernd, We tried installing 11.3.5 from buster-backports-sloppy and see the same core dump issue. We downloaded the 11.3.5 stable source code tried to build the code and install with below steps autoreconf -i ./configure make sudo make install sudo ldconfig Installation was successful and didn't see the core. Now we are trying to build the code on other Debian 10 vm, we are seeing lot of dependency issues like pam, mspack, glib2, pkg-config, xml2, etc while running "./configure". How to resolve these dependencies, Is there are any specific steps to perform before running the above commands. Is there a way to generate a build/package libs where build is generated successfully. Thanks, Girish Internal Use - Confidential -Original Message- From: Bernd Zeimetz Sent: Tuesday, March 8, 2022 7:36 PM To: Chilukuri, Girish - Dell Team; 1006...@bugs.debian.org Cc: Singh, Harmeet - Dell Team; Paturu, Santhosh - Dell Team Subject: Re: Bug#1006744: open-vm-tools core dump on debian 10 [EXTERNAL EMAIL] Hi Girish, could you give 11.3.5 from buster-backports-sloppy a try please? If that doesn't fix it, 12.0 was released recently, but that will take a bit until packages are ready. You could download it from gthub and build/test it, though. Also - please note that bullseye is the current stable release. Bernd On 2022-03-08 11:18, Chilukuri, Girish - Dell Team wrote: > Hi Bernd, >Debian buster we are using. > > Thanks, > Girish > > > Internal Use - Confidential > > -Original Message- > From: Bernd Zeimetz > Sent: Tuesday, March 8, 2022 2:13 PM > To: Chilukuri, Girish - Dell Team; 1006...@bugs.debian.org > Cc: Singh, Harmeet - Dell Team; Paturu, Santhosh - Dell Team > Subject: Re: Bug#1006744: open-vm-tools core dump on debian 10 > > > [EXTERNAL EMAIL] > > Hi, > > did you actually install the debug packages? The backtrace doesn't > look like that. > Please do so. > > https://urldefense.com/v3/__https://wiki.debian.org/HowToGetABacktrace > __;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76w > Y7MGw9htYJ8$ > [wiki[.]debian[.]org] > > Which release are you using? Bullseye? Or something else? What is > "your product"? > > > Thanks, > > Bernd > > On 2022-03-08 07:37, Chilukuri, Girish - Dell Team wrote: >> Hi Bernd, >> Below is the full backtrace from all threads from the >> core file. >> >> gdb /usr/bin/vmtoolsd rp_core.417 >> >> GNU gdb (Debian 8.2.1-2+b3) 8.2.1 >> Copyright (C) 2018 Free Software Foundation, Inc. >> License GPLv3+: GNU GPL version 3 or later >> <https://urldefense.com/v3/__http://gnu.org/licenses/gpl.html__;!!LpK >> I!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGF37 >> RWWE$ >> [gnu[.]org]> >> This is free software: you are free to change and redistribute it. >> There is NO WARRANTY, to the extent permitted by law. >> Type "show copying" and "show warranty" for details. >> This GDB was configured as "x86_64-linux-gnu". >> Type "show configuration" for configuration details. >> For bug reporting instructions, please see: >> <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/bugs/__; >> !!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7 >> MGIaDgDPE$ >> [gnu[.]org]>. >> Find the GDB manual and other documentation resources online at: >> >> <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/document >> ation/__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9p >> v-_z76wY7MGraty7eo$ >> [gnu[.]org]>. >> >> For help, type "help". >> Type "apropos word" to search for commands related to "word"... >> Reading symbols from /usr/bin/vmtoolsd...(no debugging symbols >> found)...done. >> [New LWP 417] >> [New LWP 1105] >> [Thread debugging using libthread_db enabled] Using host libthread_db >> library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1". >> Core was generated by `/usr/bin/vmtoolsd'. >> Program terminated with signal SIGSEGV, Segmentation fault. >> #0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120 >> 120 ../sysdeps/x86_64/multiarch/../strlen.S: No such file or >> directory. >> [Current thread is 1 (Thread 0x7f321f095780 (LWP 417))] >> (gdb) where >> #0 0x7f321f589206 in __strlen_sse2 () at >> ../sysdeps/x86_64/multiarch/../strlen.S:120 >> #1 0x7f321f56b475 in __GI___fputs_unlocked >> (str=0x7f321e2f7ac8 > 0x7f321e2f7ac8>, fp=fp@entry=0x55d222325690
Bug#1006744: open-vm-tools core dump on debian 10
Hi Girish, could you give 11.3.5 from buster-backports-sloppy a try please? If that doesn't fix it, 12.0 was released recently, but that will take a bit until packages are ready. You could download it from gthub and build/test it, though. Also - please note that bullseye is the current stable release. Bernd On 2022-03-08 11:18, Chilukuri, Girish - Dell Team wrote: Hi Bernd, Debian buster we are using. Thanks, Girish Internal Use - Confidential -Original Message- From: Bernd Zeimetz Sent: Tuesday, March 8, 2022 2:13 PM To: Chilukuri, Girish - Dell Team; 1006...@bugs.debian.org Cc: Singh, Harmeet - Dell Team; Paturu, Santhosh - Dell Team Subject: Re: Bug#1006744: open-vm-tools core dump on debian 10 [EXTERNAL EMAIL] Hi, did you actually install the debug packages? The backtrace doesn't look like that. Please do so. https://urldefense.com/v3/__https://wiki.debian.org/HowToGetABacktrace__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGw9htYJ8$ [wiki[.]debian[.]org] Which release are you using? Bullseye? Or something else? What is "your product"? Thanks, Bernd On 2022-03-08 07:37, Chilukuri, Girish - Dell Team wrote: Hi Bernd, Below is the full backtrace from all threads from the core file. gdb /usr/bin/vmtoolsd rp_core.417 GNU gdb (Debian 8.2.1-2+b3) 8.2.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://urldefense.com/v3/__http://gnu.org/licenses/gpl.html__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGF37RWWE$ [gnu[.]org]> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/bugs/__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGIaDgDPE$ [gnu[.]org]>. Find the GDB manual and other documentation resources online at: <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/documentation/__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGraty7eo$ [gnu[.]org]>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/vmtoolsd...(no debugging symbols found)...done. [New LWP 417] [New LWP 1105] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/vmtoolsd'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120 120 ../sysdeps/x86_64/multiarch/../strlen.S: No such file or directory. [Current thread is 1 (Thread 0x7f321f095780 (LWP 417))] (gdb) where #0 0x7f321f589206 in __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120 #1 0x7f321f56b475 in __GI___fputs_unlocked (str=0x7f321e2f7ac8 , fp=fp@entry=0x55d222325690) at iofputs_u.c:34 #2 0x7f321f5e4868 in __GI___vsyslog_chk (pri=, flag=1, fmt=0x7f321edc083c "%s.", ap=0x7ffd36e1eda0) at ../misc/syslog.c:205 #3 0x7f321f5e4dff in __syslog_chk (pri=, flag=, fmt=) at ../misc/syslog.c:129 #4 0x7f321edbb1db in Audit_EventV () at /lib/libvgauth.so.0 #5 0x7f321edbb2a4 in Audit_Event () at /lib/libvgauth.so.0 #6 0x7f321edb7f95 in VGAuth_AuditEvent () at /lib/libvgauth.so.0 #7 0x7f321edb6d05 in VGAuth_ValidateUsernamePassword () at /lib/libvgauth.so.0 #8 0x7f321edd1cf1 in () at /usr/lib/open-vm-tools/plugins/common/libvix.so #9 0x7f321edd22e3 in () at /usr/lib/open-vm-tools/plugins/common/libvix.so #10 0x7f321edd25d9 in () at /usr/lib/open-vm-tools/plugins/common/libvix.so #11 0x7f321edd81f6 in () at /usr/lib/open-vm-tools/plugins/common/libvix.so #12 0x7f321edcf2cb in () at /usr/lib/open-vm-tools/plugins/common/libvix.so #13 0x7f3221a5f664 in RpcChannel_Dispatch () at /lib/libvmtools.so.0 #14 0x7f3221a611de in () at /lib/libvmtools.so.0 #15 0x7f3221a61aa4 in () at /lib/libvmtools.so.0 #16 0x7f32218dfe98 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f32218e0288 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f32218e0582 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x55d221850bb6 in () #20 0x55d22184fcc7 in main () (gdb) thread apply all bt Thread 2 (Thread 0x7f321ed23700 (LWP 1105)): #0 0x7f321f5df819 in __GI___poll (fds=0x55d22231b050, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f32218e01f6 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f32218e031c
Bug#1006744: open-vm-tools core dump on debian 10
Hi Bernd, Debian buster we are using. Thanks, Girish Internal Use - Confidential -Original Message- From: Bernd Zeimetz Sent: Tuesday, March 8, 2022 2:13 PM To: Chilukuri, Girish - Dell Team; 1006...@bugs.debian.org Cc: Singh, Harmeet - Dell Team; Paturu, Santhosh - Dell Team Subject: Re: Bug#1006744: open-vm-tools core dump on debian 10 [EXTERNAL EMAIL] Hi, did you actually install the debug packages? The backtrace doesn't look like that. Please do so. https://urldefense.com/v3/__https://wiki.debian.org/HowToGetABacktrace__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGw9htYJ8$ [wiki[.]debian[.]org] Which release are you using? Bullseye? Or something else? What is "your product"? Thanks, Bernd On 2022-03-08 07:37, Chilukuri, Girish - Dell Team wrote: > Hi Bernd, > Below is the full backtrace from all threads from the core > file. > > gdb /usr/bin/vmtoolsd rp_core.417 > > GNU gdb (Debian 8.2.1-2+b3) 8.2.1 > Copyright (C) 2018 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <https://urldefense.com/v3/__http://gnu.org/licenses/gpl.html__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGF37RWWE$ > [gnu[.]org]> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/bugs/__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGIaDgDPE$ > [gnu[.]org]>. > Find the GDB manual and other documentation resources online at: > > <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/documentation/__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGraty7eo$ > [gnu[.]org]>. > > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from /usr/bin/vmtoolsd...(no debugging symbols > found)...done. > [New LWP 417] > [New LWP 1105] > [Thread debugging using libthread_db enabled] > Using host libthread_db library > "/usr/lib/x86_64-linux-gnu/libthread_db.so.1". > Core was generated by `/usr/bin/vmtoolsd'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120 > 120 ../sysdeps/x86_64/multiarch/../strlen.S: No such file or > directory. > [Current thread is 1 (Thread 0x7f321f095780 (LWP 417))] > (gdb) where > #0 0x7f321f589206 in __strlen_sse2 () at > ../sysdeps/x86_64/multiarch/../strlen.S:120 > #1 0x7f321f56b475 in __GI___fputs_unlocked > (str=0x7f321e2f7ac8 0x7f321e2f7ac8>, fp=fp@entry=0x55d222325690) > at iofputs_u.c:34 > #2 0x7f321f5e4868 in __GI___vsyslog_chk (pri=, > flag=1, fmt=0x7f321edc083c "%s.", ap=0x7ffd36e1eda0) > at ../misc/syslog.c:205 > #3 0x7f321f5e4dff in __syslog_chk (pri=, > flag=, fmt=) > at ../misc/syslog.c:129 > #4 0x7f321edbb1db in Audit_EventV () at /lib/libvgauth.so.0 > #5 0x7f321edbb2a4 in Audit_Event () at /lib/libvgauth.so.0 > #6 0x7f321edb7f95 in VGAuth_AuditEvent () at /lib/libvgauth.so.0 > #7 0x7f321edb6d05 in VGAuth_ValidateUsernamePassword () at > /lib/libvgauth.so.0 > #8 0x7f321edd1cf1 in () at > /usr/lib/open-vm-tools/plugins/common/libvix.so > #9 0x7f321edd22e3 in () at > /usr/lib/open-vm-tools/plugins/common/libvix.so > #10 0x7f321edd25d9 in () at > /usr/lib/open-vm-tools/plugins/common/libvix.so > #11 0x7f321edd81f6 in () at > /usr/lib/open-vm-tools/plugins/common/libvix.so > #12 0x7f321edcf2cb in () at > /usr/lib/open-vm-tools/plugins/common/libvix.so > #13 0x7f3221a5f664 in RpcChannel_Dispatch () at > /lib/libvmtools.so.0 > #14 0x7f3221a611de in () at /lib/libvmtools.so.0 > #15 0x7f3221a61aa4 in () at /lib/libvmtools.so.0 > #16 0x7f32218dfe98 in g_main_context_dispatch () at > /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #17 0x7f32218e0288 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #18 0x7f32218e0582 in g_main_loop_run () at > /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #19 0x55d221850bb6 in () > #20 0x55d22184fcc7 in main () > (gdb) thread apply all bt > > Thread 2 (Thread 0x7f321ed23700 (LWP 1105)): > #0 0x7f321f5df819 in __GI___poll (fds=0x55d22231b050, nfds=1, > timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 > #1 0x7f32218e01f6 in (
Bug#1006744: open-vm-tools core dump on debian 10
0
parser = {currentPtr = 0x555e1ca8 "", endPtr = 0x555e1ca9
"\005"}
__FUNCTION__ = "VixToolsInitiateFileTransferFromGuest"
err = 0
resultValue = 0x0
resultValueLength = 0
mustSetResultValueLength = 1 '\001'
deleteResultValue = 0 '\000'
__FUNCTION__ = "VixTools_ProcessVixCommand"
#13 0x7549e1f6 in VixTools_ProcessVixCommand
(requestMsg=requestMsg@entry=0x555e1c38,
requestName=requestName@entry=0x555db050 "4d3cb141d224fba",
maxResultBufferSize=maxResultBufferSize@entry=65444,
confDictRef=confDictRef@entry=0x55581c50,
eventQueue=eventQueue@entry=0x5558a100,
resultBuffer=resultBuffer@entry=0x7fffe008, resultLen=0x7fffe010,
deleteResultBufferResult=0x7fffe007 "") at vixTools.c:10962
err = 0
resultValue = 0x0
resultValueLength = 0
mustSetResultValueLength = 1 '\001'
deleteResultValue = 0 '\000'
__FUNCTION__ = "VixTools_ProcessVixCommand"
#14 0x754952cb in ToolsDaemonTcloReceiveVixCommand
(data=0x7fffe150) at foundryToolsDaemon.c:1248
err =
additionalError = 0
requestName = 0x555db050 "4d3cb141d224fba"
requestMsg = 0x555e1c38
maxResultBufferSize = 65444
tcloBufferLen =
resultValue = 0x0
resultValueLength = 0
deleteResultValue = 0 '\000'
destPtr = 0x0
tcloBuffer = '\000'
ctx =
eventQueue = 0x5558a100
confDictRef = 0x55581c50
__FUNCTION__ = "ToolsDaemonTcloReceiveVixCommand"
#15 0x77f77664 in RpcChannel_Dispatch () at /usr/lib/libvmtools.so.0
#16 0x77f791de in () at /usr/lib/libvmtools.so.0
#17 0x77f79aa4 in () at /usr/lib/libvmtools.so.0
#18 0x77df7e98 in g_main_context_dispatch () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x77df8288 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x000077df8582 in g_main_loop_run () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x9bb6 in ToolsCoreRunLoop (state=0x55562540 ) at
mainLoop.c:369
#22 0x9bb6 in ToolsCoreRunLoop (state=0x55562540 ) at
mainLoop.c:301
#23 0x8cc7 in main (argc=1, argv=,
envp=0x7fffe4f8) at mainPosix.c:283
i =
ret = 1
argvCopy = 0x0
src = 0x5558d800
Thanks,
Girish
Internal Use - Confidential
-Original Message-
From: Bernd Zeimetz
Sent: Tuesday, March 8, 2022 2:13 PM
To: Chilukuri, Girish - Dell Team; 1006...@bugs.debian.org
Cc: Singh, Harmeet - Dell Team; Paturu, Santhosh - Dell Team
Subject: Re: Bug#1006744: open-vm-tools core dump on debian 10
[EXTERNAL EMAIL]
Hi,
did you actually install the debug packages? The backtrace doesn't look like
that.
Please do so.
https://urldefense.com/v3/__https://wiki.debian.org/HowToGetABacktrace__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGw9htYJ8$
[wiki[.]debian[.]org]
Which release are you using? Bullseye? Or something else? What is "your
product"?
Thanks,
Bernd
On 2022-03-08 07:37, Chilukuri, Girish - Dell Team wrote:
> Hi Bernd,
> Below is the full backtrace from all threads from the core
> file.
>
> gdb /usr/bin/vmtoolsd rp_core.417
>
> GNU gdb (Debian 8.2.1-2+b3) 8.2.1
> Copyright (C) 2018 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <https://urldefense.com/v3/__http://gnu.org/licenses/gpl.html__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGF37RWWE$
> [gnu[.]org]>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/bugs/__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGIaDgDPE$
> [gnu[.]org]>.
> Find the GDB manual and other documentation resources online at:
>
> <https://urldefense.com/v3/__http://www.gnu.org/software/gdb/documentation/__;!!LpKI!0puEtOoAByFgLNggB_VMDeU15wGT9ZJdww_v-PEituwvNiosvGG9pv-_z76wY7MGraty7eo$
> [gnu[.]org]>.
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from /usr/bin/vmtoolsd...(no debugging symbols
> found)...done.
> [New LWP 417]
> [New LWP 1105]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library
> "/usr/lib/x86_64-linux-gnu/libthread_db.so.1&qu
Bug#1006744: open-vm-tools core dump on debian 10
22e3 in () at /usr/lib/open-vm-tools/plugins/common/libvix.so #10 0x7f321edd25d9 in () at /usr/lib/open-vm-tools/plugins/common/libvix.so #11 0x7f321edd81f6 in () at /usr/lib/open-vm-tools/plugins/common/libvix.so #12 0x7f321edcf2cb in () at /usr/lib/open-vm-tools/plugins/common/libvix.so #13 0x7f3221a5f664 in RpcChannel_Dispatch () at /lib/libvmtools.so.0 #14 0x7f3221a611de in () at /lib/libvmtools.so.0 #15 0x7f3221a61aa4 in () at /lib/libvmtools.so.0 #16 0x7f32218dfe98 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f32218e0288 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 --Type for more, q to quit, c to continue without paging--c #18 0x7f32218e0582 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x55d221850bb6 in () #20 0x55d22184fcc7 in main () (gdb) Thanks, Girish Internal Use - Confidential -Original Message- From: Bernd Zeimetz Sent: Monday, March 7, 2022 9:53 PM To: Chilukuri, Girish - Dell Team; 1006...@bugs.debian.org Cc: Singh, Harmeet - Dell Team; Paturu, Santhosh - Dell Team Subject: Re: Bug#1006744: open-vm-tools core dump on debian 10 [EXTERNAL EMAIL] Hi, Core file was generated and below is the segmentation fault information from core dump file: Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/vmtoolsd'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65 65 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. is that the full backtrace? Please install the debug packages and get the backtrace from all threads from the core file. (gdb) where (gdb) thread apply all bt Thanks, Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#1006744: open-vm-tools core dump on debian 10
3221a5f664 in RpcChannel_Dispatch () at /lib/libvmtools.so.0 #14 0x7f3221a611de in () at /lib/libvmtools.so.0 #15 0x7f3221a61aa4 in () at /lib/libvmtools.so.0 #16 0x7f32218dfe98 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f32218e0288 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 --Type for more, q to quit, c to continue without paging--c #18 0x7f32218e0582 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x55d221850bb6 in () #20 0x55d22184fcc7 in main () (gdb) Thanks, Girish Internal Use - Confidential -Original Message- From: Bernd Zeimetz Sent: Monday, March 7, 2022 9:53 PM To: Chilukuri, Girish - Dell Team; 1006...@bugs.debian.org Cc: Singh, Harmeet - Dell Team; Paturu, Santhosh - Dell Team Subject: Re: Bug#1006744: open-vm-tools core dump on debian 10 [EXTERNAL EMAIL] Hi, > Core file was generated and below is the segmentation fault > information from core dump file: > > Using host libthread_db library > "/usr/lib/x86_64-linux-gnu/libthread_db.so.1". > Core was generated by `/usr/bin/vmtoolsd'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65 > 65 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or > directory. is that the full backtrace? Please install the debug packages and get the backtrace from all threads from the core file. (gdb) where (gdb) thread apply all bt Thanks, Bernd -- Bernd ZeimetzDebian GNU/Linux Developer https://urldefense.com/v3/__http://bzed.de__;!!LpKI!zZ1q1iaiXuSRjd7AP_DSqk3vaJYBERm6UFwpi_0C1E_A0YRa6yV6vRdQMmON9zGHFSIVSeM$ [bzed[.]de] https://urldefense.com/v3/__http://www.debian.org__;!!LpKI!zZ1q1iaiXuSRjd7AP_DSqk3vaJYBERm6UFwpi_0C1E_A0YRa6yV6vRdQMmON9zGHgzcEI9U$ [debian[.]org] GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#1006744: open-vm-tools core dump on debian 10
Hi, Core file was generated and below is the segmentation fault information from core dump file: Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/vmtoolsd'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65 65 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. is that the full backtrace? Please install the debug packages and get the backtrace from all threads from the core file. (gdb) where (gdb) thread apply all bt Thanks, Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#1006744: open-vm-tools core dump on debian 10
Package: open-vm-tools Version: 10.3.10-1+deb10u2 Hi, We are using Debian 10(amd 64) in our product and see core dump generated by “/usr/bin/vmtoolsd”. We tried with open-vm-tools 11.2.5 and 10.1.5 versions still see the same issue. Package details: dpkg --list open-vm-tools Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii open-vm-tools 2:10.3.10-1+deb10u2 amd64Open VMware Tools for virtual machines hosted on VMware (CLI) OS details: PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian HOME_URL=https://www.debian.org/ SUPPORT_URL=https://www.debian.org/support BUG_REPORT_URL=https://bugs.debian.org/ Core file was generated and below is the segmentation fault information from core dump file: Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/vmtoolsd'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65 65 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. systemctl status open-vm-tools.service ● open-vm-tools.service - Service for virtual machines hosted on VMware Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Tue 2022-03-01 08:32:44 UTC; 26min ago Docs: http://open-vm-tools.sourceforge.net/about.php Process: 441 ExecStart=/usr/bin/vmtoolsd (code=dumped, signal=SEGV) Main PID: 441 (code=dumped, signal=SEGV) Mar 01 08:27:11 systemd[1]: Started Service for virtual machines hosted on VMware. Mar 01 08:32:44 systemd[1]: open-vm-tools.service: Main process exited, code=dumped, st Mar 01 08:32:44 systemd[1]: open-vm-tools.service: Failed with result 'core-dump'. Thanks, Girish Internal Use - Confidential
