On Sat, Mar 19, 2011 at 01:19:40PM +0100, Nicolas wrote:
> If you enable the device protection with a password. bjdwp doesn't work.
> (but works well if you remove the device password protection).
Hi Nicolas,
I'm not sure where we are for this issue... does password support work
yet for bjdwp?
T
Le mardi 15 mars 2011 à 21:45 -0400, Chris Frey a écrit :
> Thanks again Nicolas and Toby, for your quick response and testing.
>
> I believe the password bugs are fixed now. And the btool error display
> bug, which was from a different change, not socket related.
>
> There's still one sequence
Thanks again Nicolas and Toby, for your quick response and testing.
I believe the password bugs are fixed now. And the btool error display
bug, which was from a different change, not socket related.
There's still one sequence packet issue with multi-database backups
with barrybackup, but that's
On Sun, Mar 13, 2011 at 08:47:59PM +0100, Nicolas wrote:
> Unfortunatly, I have some regressions:
> - bjdwp KO with all my devices
I've made a change to SocketBase::PacketJVM() to go back to non-automatic
sequence packet checking, just for that function.
Could you give it another test? I don't h
On Tue, Mar 15, 2011 at 05:15:16PM +, Toby Gray wrote:
> Those changes looks good. The asynchronous callback version of the raw
> channel didn't initially work, but it was just a case of pulling out all
> the complex semaphore stuff that it had been doing which is now handled
> more sensibly
Hi Chris,
Those changes looks good. The asynchronous callback version of the raw
channel didn't initially work, but it was just a case of pulling out all
the complex semaphore stuff that it had been doing which is now handled
more sensibly in the socket class.
I've made the necessary changes i
