Hi,
I find I have to remove the
signal(SIGBUS, inkscape_segv_handler)
from inkscape.cpp in order to compile on Windows. My MinGW doesn't seem to know anything about SIGBUS. Does it work for anyone else?
Thanks
Carl
Carl Hetherington wrote:
Hi,
I find I have to remove the
signal(SIGBUS, inkscape_segv_handler)
from inkscape.cpp in order to compile on Windows. My MinGW doesn't seem to know anything about SIGBUS. Does it work for anyone else?
Thanks
Carl
Yeah, I got that in the transcript from the autobuild last night. I -SWEAR- that I tested this before I committed. I think this might be a difference in the versions of mingw-runtime.
I guess we need to #ifdef that for now. I hate those things! ;)
Bob
Bob Jamison wrote:
I guess we need to #ifdef that for now. I hate those things! ;)
Never mind..... I see that it is already done.
Bob
From MAILER-DAEMON Wed Jun 23 08:46:32 2004
Date: Wed, 23 Jun 2004 17:45:46 +0200 From: Thorsten Wilms <t_w_@...123...> To: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] off-topic but related: SORBS, oh sweet SORBS... Message-ID: <20040623154546.GA7545@...124...> Reply-To: tw@...125... References: <200406231316.11001.artemio-subscriptions@...411...> <20040623123141.94775.qmail@...394...> Mime-Version: 1.0 In-Reply-To: <20040623123141.94775.qmail@...394...> Priority: normal X-Mailer: Mutt User-Agent: Mutt/1.5.5.1i X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by sourceforge.net. See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 0.0 SF_CHICKENPOX_MINUS BODY: Text interparsed with - 0.0 SF_CHICKENPOX_APOSTROPHE BODY: Text interparsed with ' Sender: inkscape-devel-admin@lists.sourceforge.net Errors-To: inkscape-devel-admin@lists.sourceforge.net X-BeenThere: inkscape-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Unsubscribe: https://lists.sourceforge.net/lists/listinfo/inkscape-devel, mailto:inkscape-devel-request@lists.sourceforge.net?subject=unsubscribe List-Id: <inkscape-devel.lists.sourceforge.net> List-Post: mailto:inkscape-devel@lists.sourceforge.net List-Help: mailto:inkscape-devel-request@lists.sourceforge.net?subject=help List-Subscribe: https://lists.sourceforge.net/lists/listinfo/inkscape-devel, mailto:inkscape-devel-request@lists.sourceforge.net?subject=subscribe List-Archive: http://sourceforge.net/mailarchive/forum.php?forum=inkscape-devel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Content-Disposition: inline
If this doesn't get through, I will know what happened to my last post. Otherwise let me just say sorry!
On Wed, 2004-06-23 at 09:26, Carl Hetherington wrote:
Hi,
I find I have to remove the
signal(SIGBUS, inkscape_segv_handler)
from inkscape.cpp in order to compile on Windows. My MinGW doesn't seem to know anything about SIGBUS. Does it work for anyone else?
As far as I know, Windows doesn't actually have SIG-anything. I guess that's a MinGW-provided stub or emulation of some kind.
We should probably set up some kind of feature test macro for this, rather than using #ifdefs for various compiler/OS combinations.
-mental
On Thu, 24 Jun 2004 00:42:17 -0400, MenTaLguY wrote:
As far as I know, Windows doesn't actually have SIG-anything. I guess that's a MinGW-provided stub or emulation of some kind.
Most likely. If you want to do crash handling on Windows you need to surround your program or main loop with an SEH frame.
thanks -mike
participants (4)
-
Bob Jamison -
Carl Hetherington -
MenTaLguY -
Mike Hearn