Searched +hist:8 +hist:b9099b1 (Results 1 - 4 of 4) sorted by relevance
| /haiku/src/apps/debugger/user_interface/cli/ | ||
| H A D | CliContext.cpp | diff 8b9099b1 Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8b9099b1 Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8fe9f8b2 Fri Jul 27 15:41:11 MDT 2012 Ingo Weinhold <ingo_weinhold@gmx.de> Debugger CLI: Move more stuff to and extend CliContext * Move the libedit interface there and provide nicer to use methods. * Also start adding utility methods for the input loop. It is going to manage all interactions of the input loop with outside events. * Fix the "quit" command. The user is now prompted what to do with the debugged team and the input loop thread avoids reentering the input loop. diff 8b9099b1b24358076e28f6e3a894e6f39de4cece Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8fe9f8b2d0e3c8f88406f5720a1d2027638c43b6 Fri Jul 27 15:41:11 MDT 2012 Ingo Weinhold <ingo_weinhold@gmx.de> Debugger CLI: Move more stuff to and extend CliContext * Move the libedit interface there and provide nicer to use methods. * Also start adding utility methods for the input loop. It is going to manage all interactions of the input loop with outside events. * Fix the "quit" command. The user is now prompted what to do with the debugged team and the input loop thread avoids reentering the input loop. |
| H A D | CliContext.h | diff 8b9099b1 Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8b9099b1 Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8fe9f8b2 Fri Jul 27 15:41:11 MDT 2012 Ingo Weinhold <ingo_weinhold@gmx.de> Debugger CLI: Move more stuff to and extend CliContext * Move the libedit interface there and provide nicer to use methods. * Also start adding utility methods for the input loop. It is going to manage all interactions of the input loop with outside events. * Fix the "quit" command. The user is now prompted what to do with the debugged team and the input loop thread avoids reentering the input loop. diff 8b9099b1b24358076e28f6e3a894e6f39de4cece Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8fe9f8b2d0e3c8f88406f5720a1d2027638c43b6 Fri Jul 27 15:41:11 MDT 2012 Ingo Weinhold <ingo_weinhold@gmx.de> Debugger CLI: Move more stuff to and extend CliContext * Move the libedit interface there and provide nicer to use methods. * Also start adding utility methods for the input loop. It is going to manage all interactions of the input loop with outside events. * Fix the "quit" command. The user is now prompted what to do with the debugged team and the input loop thread avoids reentering the input loop. |
| H A D | CommandLineUserInterface.h | diff 8b9099b1 Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8b9099b1 Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8fe9f8b2 Fri Jul 27 15:41:11 MDT 2012 Ingo Weinhold <ingo_weinhold@gmx.de> Debugger CLI: Move more stuff to and extend CliContext * Move the libedit interface there and provide nicer to use methods. * Also start adding utility methods for the input loop. It is going to manage all interactions of the input loop with outside events. * Fix the "quit" command. The user is now prompted what to do with the debugged team and the input loop thread avoids reentering the input loop. diff 8b9099b1b24358076e28f6e3a894e6f39de4cece Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8fe9f8b2d0e3c8f88406f5720a1d2027638c43b6 Fri Jul 27 15:41:11 MDT 2012 Ingo Weinhold <ingo_weinhold@gmx.de> Debugger CLI: Move more stuff to and extend CliContext * Move the libedit interface there and provide nicer to use methods. * Also start adding utility methods for the input loop. It is going to manage all interactions of the input loop with outside events. * Fix the "quit" command. The user is now prompted what to do with the debugged team and the input loop thread avoids reentering the input loop. |
| H A D | CommandLineUserInterface.cpp | diff 8b9099b1 Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8b9099b1 Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8fe9f8b2 Fri Jul 27 15:41:11 MDT 2012 Ingo Weinhold <ingo_weinhold@gmx.de> Debugger CLI: Move more stuff to and extend CliContext * Move the libedit interface there and provide nicer to use methods. * Also start adding utility methods for the input loop. It is going to manage all interactions of the input loop with outside events. * Fix the "quit" command. The user is now prompted what to do with the debugged team and the input loop thread avoids reentering the input loop. diff 8b9099b1b24358076e28f6e3a894e6f39de4cece Tue Nov 04 15:38:43 MST 2014 Rene Gollent <rene@gollent.com> Debugger: Fix #11411. CliContext/CommandLineUserInterface: - Process the debug report event asynchronously. The missing lock that was fixed in commit 5ac34e5a78305abac4c758a34db9f1e34aee54ed highlighted a problem in how the CLI was handling the case where it was intended to exit immediately after saving a report, since it issued the quit request directly from the report event handler. This resulted in locking issues, as the team debugger would then attempt to tear itself down, during which it needs to acquire the team lock. However, that was already being held by the thread in which the CLI was initiating the quit, resulting in a deadlock. diff 8fe9f8b2d0e3c8f88406f5720a1d2027638c43b6 Fri Jul 27 15:41:11 MDT 2012 Ingo Weinhold <ingo_weinhold@gmx.de> Debugger CLI: Move more stuff to and extend CliContext * Move the libedit interface there and provide nicer to use methods. * Also start adding utility methods for the input loop. It is going to manage all interactions of the input loop with outside events. * Fix the "quit" command. The user is now prompted what to do with the debugged team and the input loop thread avoids reentering the input loop. |
Completed in 66 milliseconds