I also had this problem on Leopard with Flex Builder 3 final release.
Deleting the first line from mm.cfg solved the problem. What I also
noticed was that when the debugger was connecting the syslogd process
was going crazy and printing the following message to the logs over
and over. I had to force quit it in order for it to stop.



!ENTRY com.adobe.flexbuilder.debug 4 2 2008-03-05 14:31:06.178
!MESSAGE Problems occurred when invoking code from plug-in:
"com.adobe.flexbuilder.debug".
!STACK 0
java.lang.NullPointerException
at
com.adobe.flexbuilder.debug.breakpoints.FlexLineBreakpoint.findSourceFiles(FlexL\
ineBreakpoint.java:388)
at
com.adobe.flexbuilder.debug.breakpoints.FlexLineBreakpoint.instantiate(FlexLineB\
reakpoint.java:442)
at
com.adobe.flexbuilder.debug.model.FlexDebugTarget.breakpointAdded(FlexDebugTarge\
t.java:889)
at
com.adobe.flexbuilder.debug.model.FlexDebugTarget$FdbThread.installDeferredBreak\
points(FlexDebugTarget.java:539)
at
com.adobe.flexbuilder.debug.model.FlexDebugTarget$FdbThread.advanceStateMachine(\
FlexDebugTarget.java:570)
at
com.adobe.flexbuilder.debug.model.FlexDebugTarget$FdbThread.access$6(FlexDebugTa\
rget.java:544)
at
com.adobe.flexbuilder.debug.model.FlexDebugTarget$1.run(FlexDebugTarget.java:646\
)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:857)
at
com.adobe.flexbuilder.debug.model.FlexDebugTarget$FdbThread.eventLoop(FlexDebugT\
arget.java:626)
at
com.adobe.flexbuilder.debug.model.FlexDebugTarget$FdbThread.run(FlexDebugTarget.\
java:687)
at java.lang.Thread.run(Thread.java:613)


--- In flexcoders@yahoogroups.com, Bjorn Schultheiss
<bjorn.mailinglists@...> wrote:
>
> > Can you please make sure that you are trying to profile a debug
> > version of the swf?
>
> I haven't created a release build in 2 months.
> I dont use ant or command-line for compiling debug builds. Only the ide.
>
> > it could be due to an entry
> > in the mm.cfg file left behind by the profiler.
>
> You were correct about the profile leaving behind the entry in mm.cfg
>
>
>
>
> On 31/01/2008, at 3:24 PM, Gaurav Jain wrote:
>
> > Profiler is not supposed to work with release swfs.
> >
> > Can you please make sure that you are trying to profile a debug
> > version of the swf? If the profiler is giving the error message for a
> > debug swf, can you please log a bug at http://bugs.adobe.com/flex with
> > the swf file, please?
> >
> > If debug is not working after profiling, it could be due to an entry
> > in the mm.cfg file left behind by the profiler. So if you remove the
> > entry the debugger should start working again.
> >
> > On OS X the mm.cfg should be in the home directory and the entry
> > starts with PreloadSwf=
> >
> > Thanks,
> > Gaurav
> >
> > --- In flexcoders@yahoogroups.com, Bjorn Schultheiss
> > <bjorn.mailinglists@> wrote:
> > >
> > > Hey,
> > >
> > > I've been getting this annoying bug where,
> > >
> > > after debugging an app i try to profile it,
> > > profiler throws an error 'can't profiler a non debug version', wtf!,
> > > then i try to debug and debug session wont load!
> > >
> > > my current workaround for getting debug to work is to rename or
> > remove
> > > the ProfilerAgent.swf in
> > >
> > $
> > Workspace
> > :.metadata:.plugins:com.adobe.flash.profiler:ProfilerAgent.swf
> > >
> > > In on mac in FB3b3
> > >
> >
> >
> >
>