Memory error in MacDroidNotifier on Intel dual core 64 bit

[GoogleCodeExporter]

What steps will reproduce the problem?
1. tail -f /var/log/system.log
2. with MacDroidNotifier running, send test notification from phone
3.

What is the expected output? What do you see instead?
Test notification from growl.  Errors in system.log

What version of the product are you using? On what operating system?
0.2.3. OS X 10.5.8 with this hardware:
  Model Name:   MacBook Pro
  Model Identifier: MacBookPro4,1
  Processor Name:   Intel Core 2 Duo
  Processor Speed:  2.4 GHz
  Number Of Processors: 1
  Total Number Of Cores:    2
  L2 Cache: 3 MB
  Memory:   2 GB
  Bus Speed:    800 MHz
  Boot ROM Version: MBP41.00C1.B00
  SMC Version (system): 1.27f2

Please provide any additional information below.
I'm getting an error on the mac end.  From system.log:

Apr 22 12:11:05 Casa-Quetzal kernel[0]: IOMemoryDescriptor: attempt to
create 32b
virtual in 64b task, use ::withAddressRange()
Apr 22 12:11:05 Casa-Quetzal kernel[0]: Backtrace 0x430605 0x4304f5
0x42ff40 0xa947f3
0xa946bd 0xa93fec 0x427525
Apr 22 12:11:05 Casa-Quetzal kernel[0]: Kernel loadable modules in
backtrace (with
dependencies):
Apr 22 12:11:05 Casa-Quetzal kernel[0]:
com.apple.iokit.IOBluetoothFamily(2.1.9f10)@0xa6b000->0xaa4fff

I did a build from trunk, setting the output to architecture native to the
build machine and that works.  No idea why the universal build doesn't work.  

Original issue reported on code.google.com by mccann....@gmail.com on 22 Apr 2010 at 7:47

[GoogleCodeExporter]

Since you have it running from within xcode, can you get me an actual stack 
trace for when this happens? 
(instead of just addresses) It looks like a 64-bit issue.

Original comment by rdamazio@gmail.com on 22 Apr 2010 at 8:13

• Changed state: Accepted
• Added labels: OpSys-OSX

[GoogleCodeExporter]

I can't reproduce this in the debugger.  Would the symbols directory help?

Original comment by mccann....@gmail.com on 23 Apr 2010 at 5:33

[GoogleCodeExporter]

Hmmm I don't think so (since the backtrace above is a kernel backtrace, not the 
app's).
I've just submitted a few minor changes to the compilation in r158, can you 
update your copy and try again with 
the universal binary?

Original comment by rdamazio@gmail.com on 24 Apr 2010 at 5:31

[GoogleCodeExporter]

Ping?

Original comment by rdamazio@gmail.com on 5 Aug 2010 at 8:15

[GoogleCodeExporter]

Unable to reproduce, and got no further feedback from reporter, so I'm closing 
it.

Original comment by rdamazio@gmail.com on 29 Aug 2010 at 7:47

• Changed state: Invalid