Am Freitag, 2. März 2007 schrieb Ari Johnson: > On 2/26/07, Dennis Schridde <[EMAIL PROTECTED]> wrote: > > Am Sonntag, 25. Februar 2007 schrieb Giel van Schijndel: > > > [EMAIL PROTECTED] schreef: > > > > I can not even reads the text that should be in ""Warzone crashed > > > > unexpectedly, would you like to save a diagnostic file?" When it > > > > crash. > > > > > > > > I just get a bunch of sqaure characters. > > > > > > > > Another problem is it is hardcoded to use c:\temp even if there is > > > > no c:\temp! > > > > Then I assume I get message of "Failed to create dump file " but I > > > > can not reads this either, it shows square blocks for text again. > > > > > > > > This is windows with compiler VS2005. > > > > > > It uses the temp directory from my profile on my pc (e.g. docs & > > > settings/user/local settings/temp) > > > > Yes, C:\temp is just a fallback... Maybe we need to improve this... > > Per default it should use GetTempPath(), which should be present on > > nearly any Windows version. > > --Dennis > > Can you add some code to check for availability of this in configure? > execinfo.h is not available on the Mac, so Warzone won't build on the > Mac anymore (not even 2.0.x). Sure. I could add some HAVE_EXECINFO_H define, probably. Another way would be to add a 3rd codepath to lib/framework/exceptionhandler.c to handle MacOS. (Even an empty path would be possible as a workaround.) execinfo.h should be present on all GNU systems (Linux or Arch is what I know of) running glibc. If BSD also uses glibc, then it should work there too.
--Dennis
pgpLdA54S76Cl.pgp
Description: PGP signature
_______________________________________________ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
