I get it under this scenario
1) I build my project (NW: Debugging is enabled)
2) I start debugging the application
3) I start the application via the debugger and do some, well, debuggy stuff
4) I kill the debug session
5) I rebuild my project
6) I start a new debugging session
At this point, I can reliably get the BDWM error message.
Now if I add the following step between steps 3 and 4
3 1/2) I issue a STOP (cursive-l-..-1)
I've got a 50/50 chance that I can run the debugger again (and not get the
BDWM error message).
Some people have said they only get it when the constructor is running - it
doesn't matter to me.
My guess is that there is some Windows funky-ness that's causing this to
happen (not enough resources/memory/whatever).
(As to my previous post, I'd just seen the posting I replied to and I'd
just been bit by it again, and I was in crush mode. BTW, I must say that
I've been working with the GNU tools for the past 2 years and just switched
over to Codewarrior, I am very happy with the product, it's saved me oodles
of time on some new work I'm doing.)
At 02:17 PM 12/7/99 -0500, you wrote:
>For what it's worth, I get this message when:
>
>1. I've been debugging, AND
>2. I kill the debug session, resetting the device, AND
>3. I then close the Emulator and start a new one.
>
>For some reason the debugger is unable to connect to the new Emulator
>process.
>
>oge
>
> > -----Original Message-----
> > From: Jun-Kiat Lam [SMTP:[EMAIL PROTECTED]]
> > Sent: Monday, December 06, 1999 17:44
> > To: [EMAIL PROTECTED]
> > Subject: Debugger woes and other issues
> >
> > Hello all,
> >
> > I apologize for the delay in replying to your issues. I had been in crunch
> > mode with another product and have not been able to look at Palm issues as
> > much recently. With regards to the debugger issues, the 'BDWM' message
> > itself is a bug, but typically indicates that the debugger has failed to
> > connect to the emulator. For long-timers, it is the same message as the
> > 'failed to connect to remote' in previous release of CodeWarrior for Palm.
> > There are number of reasons this may be happening:
> >
> > a) an invalid .prc has been generated that is rejected by the Palm OS
> > Emulator or the device. This typically happens when your app overruns the
> > 64K per segment limit of the Palm OS. The acid test for it is to try to
> > install the application directly onto the emulator or device. If it is
> > rejected then you have hit this problem.
> > b) the device has not been set in console mode, thus preventing the
> > debugger
> > from connecting. This usually happens when you enter the 'shortcut dot dot
> > 2' incorrectly (it should show up in the Find menu as 'shorcut.2' - single
> > period '.'). Also, if the serial port is tied up, the debugger will fail
> > to
> > connect as well. Make sure HotSync is off (not in the system tray on
> > Windows).
> > c) possibly incorrect combinations of the ROM and emulator that the
> > debugger
> > does not support.
> >
> > That said though, we admit that there are bugs in the debugger itself that
> > we need to fix. We (and Palm) are currently working on patches for Release
> > 6, and hope to have it soon. In the meantime, we appreciate your patience,
> > and your feedback. I hope to have beta versions of a plugin patch
> > available
> > soon that will hopefully address some of the issues you are seeing. In the
> > meantime, please continue to send bug reports to [EMAIL PROTECTED] or
> > to
> > me, Jun-Kiat Lam at [EMAIL PROTECTED] and I'll try to help as best as I
> > can.
> >
> > Again, our apologies for the inconvenience caused.
> >
> > Rgds,
> > Jun-Kiat Lam
> > Metrowerks QA Lead
> > CodeWarrior for Palm Computing platform.
> >
----
Tom Frauenhofer, [EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com
