[MLton-user] Lack of information with -const 'Exn.keepHistory true'

Nicolas Bertolotti nicolas.bertolotti at polyspace.com
Wed Jan 24 02:32:41 PST 2007


Thanks for the information.

Then, thanks to the -profile-include '<basis>', I can see the following :

exception SysErr(OS.SysErr(name="Invalid argument", syserror=inval)) raised.
 raised at: MLtonSignal.setHandler.<branch> <basis>/mlton/signal.sml 214.10
         General.o <basis>/general/general.sml 29.14
         General.o.<branch> <basis>/general/general.sml 29.23
         PosixError.SysCall.simpleResultRestart <basis>/posix/error.sml
123.42
         PosixError.SysCall.simpleResultRestart.<branch>
<basis>/posix/error.sml 124.19
         PosixError.raiseSys <basis>/posix/error.sml 51.11
         PosixError.raiseSys.<branch> <basis>/posix/error.sml 51.24
         PosixError.raiseSys.raise <basis>/posix/error.sml 51.30

This certainly helps as it gives some information on the system call that
fails.

But it still does not provide a location in my own code which could make it
easier to identify the path to the error. As a consequence, I'll need to
instrument my code in order to identify the appropriate location.

Please note that this specific crash is not really an issue. I know exactly
what I've got to do in order to solve it (I am currently porting the
application in order to compile through MinGW so I'm not really surprised it
fails when I try to catch Unix signals).

I'm just trying to find an appropriate set of options I could use while
debugging in order to get as many information as possible in order to
identify the full path to a particular error.

Thanks in advance for your help.

---------------------------------------------------------------------------
    Nicolas Bertolotti             |    PolySpace Technologies S.A.
    http://www.polyspace.com       |    28, rue Estienne d'Orves
    Phone: +33 (0)1 49 65 32 66    |    92120 Montrouge
                                   |    Std phone: +33 (0)1 49 65 32 60


> -----Original Message-----
> From: Stephen Weeks [mailto:sweeks at sweeks.com]
> Sent: mercredi 24 janvier 2007 02:19
> To: nicolas.bertolotti at polyspace.com
> Cc: mlton-user at mlton.org
> Subject: [MLton-user] Lack of information with -const 'Exn.keepHistory
> true'
> 
> 
> > exception SysErr(OS.SysErr(name="Invalid argument", syserror=inval))
> raised.
> >
> > raised at: General.o <basis>/general/general.sml 29.14
> >
> >          PosixError.raiseSys <basis>/posix/error.sml 51.11
> 
> In addition to Matthew's -profile-include suggestion, since the error
> is likely due to a failed system call, you could use strace to find
> out the call and its arguments.
-------------- next part --------------
exception SysErr(OS.SysErr(name="Invalid argument", syserror=inval)) raised.
 raised at: MLtonSignal.setHandler.<branch> <basis>/mlton/signal.sml 214.10
         General.o <basis>/general/general.sml 29.14
         General.o.<branch> <basis>/general/general.sml 29.23
         PosixError.SysCall.simpleResultRestart <basis>/posix/error.sml 123.42
         PosixError.SysCall.simpleResultRestart.<branch> <basis>/posix/error.sml 124.19
         PosixError.raiseSys <basis>/posix/error.sml 51.11
         PosixError.raiseSys.<branch> <basis>/posix/error.sml 51.24
         PosixError.raiseSys.raise <basis>/posix/error.sml 51.30


More information about the MLton-user mailing list