Re: [MirageOS-devel] contributing best practices?

[Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx>]

On 25 Mar 2014, at 22:49, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:

> One quick trick that often helps in these sorts of situations is to wrap the 
> offending code in a try/with and print the backtrace:
> 
> try
>  the_bad_code
> with exn ->
>  Printf.printf "Exn: %s\n%!" (Printexc.to_string exn);
>  Printexc.print_backtrace stdout; 
>  raise exn

didn't i add something like this to the pre-refactoring mirage at some point? 
did it get lost, or is it not possible to have now after all the refactoring?  
seems like dropping this to console before bailing out would be a useful 
default behaviour...  should i add to the mirage cli tool maybe so that main.ml 
is generated appropriately?

-- 
Cheers,

R.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel