AFAICS, there is no problem with e.msg.

[simgrid.git] / src / simix / smx_deployment.c

diff --git a/src/simix/smx_deployment.c b/src/simix/smx_deployment.c
index a26e502..f3536d7 100644 (file)
--- a/src/simix/smx_deployment.c
+++ b/src/simix/smx_deployment.c
@@ -124,10 +124,10 @@ void SIMIX_launch_application(const char *file)
   TRY {
          parse_status = surf_parse();
          surf_parse_close();
-         xbt_assert(!parse_status, "Parse error in %s", file);
+         xbt_assert(!parse_status, "Parse error at %s:%d", file,surf_parse_lineno);
   } CATCH(e) {
-         xbt_die("Unrecoverable error at %s:%d: %s", file,surf_parse_lineno,
-                         __xbt_running_ctx_fetch()->exception.msg); //FIXME: that pimple is due to the fact that e.msg does not seem to be set on CATCH(e). The pimple should be removed when the bug is gone.
+         xbt_die("Unrecoverable error at %s:%d: %s",
+                  file, surf_parse_lineno, e.msg);
   }
 }