This is not a valid bug report.

I can confirm problems  with "LibreOffice 3.5.2.2 German UI/Locale [Build-ID: 281b639-6baa1d3-ef66a77-d866f25-f36d45f] on German WIN7 Home Premium (64bit). Opening the document and allowing Macros I get lots of Basic error messages "Syntax Error. Unexpected Symbol ..." what I can confirm one by one clicking OK, but finally LibO will crash. Same with 3.4.5, .3.3., 
Some 3.5 WIN XP 32 (VirtualBox) and 3.4.4 Ubuntu (VirtualBox) 

I limit this bug to the crash problem.

@reporter:
Thank you for your report – unfortunately important information is missing. If you want to reopen additional bugs concerning the syntax error please contribute useful information. All th Bugs here are concerning problems ;-)
May be hints on <http://wiki.documentfoundation.org/BugReport> will help you to find out what information will be useful to reproduce your problem? If you believe that that  is really sophisticated please as for Help on a user mailing list
Please:
- Write a meaningful Summary describing exactly what the problem is
- Attach a sample document (not only screenshot) or refer to an existing 
  sample document in an other Bug with a link.
- Attach screenshots with comments if you believe that that might explain the 
  problem better than a text comment. Best way is to insert your screenshots
  into a DRAW document and to add comments that explain what you want to show
- Contribute a step by step instruction containing every key press and every 
  mouse click how to reproduce your problem (due to example in Bug 43431)
– if possible contribute an instruction how to create a sample document 
  from the scratch
- add information 
  -- what EXACTLY is unexpected
  -- and WHY do you believe it's unexpected (cite Help or Documentation!)
  -- concerning your PC 
  -- concerning your OS (Version (with Build ID if it's not a public release), 
     Distribution, Language)
  -- concerning your LibO version and localization (UI language, Locale setting)
  –- Libo settings that might be related to your problems 
  -- how you launch LibO and how you opened the sample document
  –- If you can contribute an OOo Issue that might be useful
  -- everything else crossing your mind after you read linked texts

Even  if you can not provide all demanded information, every little new information might bring the breakthrough.

May be you can test <https://www.libreoffice.org/get-help/bug/> for submitting bug reports?

Too poor informations, not a valid bug report.

Created attachment 91302 [details]
typescript with backtrace

Some pointers into the typescript:
   3: run-time messages from LibreOffice
  61: gdb backtrace from the core file with symbols

I am setting bug status NEW because of the crash.  I have no opinion
about whether LibreOffice should be able to load the macros; but if
it must fail, it should fail politely and informatively and without
taking all of LibreOffice with it.

I should have said:

The backtrace is from master commit 480c7c2, fetched 2012-12-27 02:33
UTC, configured as:
    --enable-option-checking=fatal
    --enable-dbgutil
    --enable-crashdump
    --without-system-postgresql
    --without-myspell-dicts
    --with-extra-buildid
    --without-doxygen
    --with-external-tar=/home/terry/lo_hacking/git/src
built and running on debian-wheezy 64-bit.

Setting importance back to normal because I am interested in this only
as an open item in bugzilla.  Anybody who encounters the problem in
actual use of LibreOffice is welcome to bump the importance up
again.