Hi, for checking an API test (take a look at Issue 78873) I do the following without success:
1. Start StarOffice like this in a shell: ./soffice "-accept=socket,host=0,port=8100;urp" -nologo -calc -norestore => I get a process soffice and a sub-process soffice.bin 2. I start gdb this way: gdb soffice.bin <PID of soffice.bin> 3. I type cont (maybe after setting some breakpoints) 4. From a different shell I call checkapi -o sch.ChXChartData::com::sun::star::chart::XChartData -tdoc <local path to testdocuments> => The office freezes, gdb no longer reacts, the API test does nothing. Without the debugger this test crashes, so I expected to do this as well with the debugger being attached. It is possible to stop the API test (checkapi) with Ctrl-C. The debugger can only be killed, same for soffice. I noticed that I get a second process soffice.bin with the same arguments than the one before, so probably it is forked for the remote access? So, where does this come from, is this a new way to do remote access? BTW, attaching with another gdb instance to this new process does not work. Please, anybody who has an idea, what can I do? -Bjoern --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
