[Mulgara-dev] Backups failing Mulgara 1.2 Windows

[Ben Hysell]

Hmm...ctrl-break in the window Mulgara is running in terminates Mulgara
with no stack trace at all.

 

More importantly, Mulgara does not survive a backup on a Windows
computer and drops to the command prompt producing the stack trace I
have already sent along.  

 

Backing up Mulgara on a Windows machine stops Mulgara dead.  It needs to
be restarted after a backup event.

 

Hence I'm not sure the proposed methods will get us what we need other
than to start tracing the code in a debugger which I will be attempting
shortly, unless anyone out there has a better method, or possibly I have
misunderstood something?

 

Thanks

 

-ben

 

 

From: mulgara-dev-bounces at mulgara.org
[mailto:mulgara-dev-bounces at mulgara.org] On Behalf Of David Makepeace
Sent: Monday, April 07, 2008 11:37 PM
To: Mulgara Developers
Subject: Re: [Mulgara-dev] Backups failing Mulgara 1.2 Windows

 

On Tue, Apr 8, 2008 at 11:34 AM, Andrae Muys <andrae at netymon.com> wrote:

 

 From a command-line ctrl-\ under any unix - I believe ctrl-break
under windows.  Also under unix sending SIGQUIT, but I don't know
what the equivalent is under windows.



You can use SendSignal to send a ctrl-break under Windows.

http://www.latenighthacking.com/projects/2003/sendSignal/
http://www.latenighthacking.com/projects/2003/sendSignal/SendSignal.exe


David.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mulgara.org/pipermail/mulgara-dev/attachments/20080408/c0a2a186/attachment.htm>