Results 1 to 10 of 10

Thread: Running from web supplied OSX bundle and built bundle

  1. #1
    Newbie
    Join Date
    Jan 2010
    Posts
    6

    Running from web supplied OSX bundle and built bundle

    I successfully ran obdgpslogger from the command line after a build from the svn (I did not try to connect to a device yet, but the program executes). However, neither the bundle on the website nor the bundle I built with cmake "make package" will run. It appears obdgui is missing when I build from the svn and it appears that the web supplied bundle crashes due to obdgui.

    First, I am running Mac OS 10.4.11 on a mid-2007 (I believe) MacBook. I used Macports to install cmake and subversion.

    Initially I tried running the .app from the webpage .dmg (v0.11). The application won't start, it crashes immediately. I have console.log info from that:

    Code:
    Jan  8 18:59:00 john-lewis-computer crashdump[1888]: obdgui crashed
    Jan  8 18:59:01 john-lewis-computer crashdump[1888]: crash report written to: /Users/jlewis/Library/Logs/CrashReporter/obdgui.crash.log
    And obdgui.crash.log gives this:

    Code:
    Host Name:      john-lewis-computer
    Date/Time:      2010-01-08 18:58:59.313 -0500
    OS Version:     10.4.11 (Build 8S2167)
    Report Version: 4
    
    Command: obdgui
    Path:    /Applications/OBD GPS Logger.app/Contents/Resources/bin/obdgui
    Parent:  WindowServer [89]
    
    Version:  ()
    
    PID:    1884
    Thread: 0
    
    Exception:  EXC_BAD_ACCESS (0x0001)
    Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
    
    Thread 0 Crashed:
    0   libSystem.B.dylib 	0x9010c456 _malloc_initialize + 36
    1   libSystem.B.dylib 	0x90002417 malloc + 29
    2   obdgui            	0x0000fee7 Fl_Input_Choice::InputMenuButton::~InputMenuButton [in-charge deleting]() + 10319
    3   obdgui            	0x00009bd3 Fl_Text_Display::buffer() + 3409
    4   obdgui            	0x000064bb Fl_Input_Choice::value(int) + 3267
    5   obdgui            	0x00005612 0x1000 + 17938
    
    Thread 0 crashed with X86 Thread State (32-bit):
      eax: 0x00000000  ebx: 0x9010c443  ecx: 0x90000b18  edx: 0x00000008
      edi: 0x00000000  esi: 0x00000000  ebp: 0xbffff5c8  esp: 0xbffff530
       ss: 0x0000001f  efl: 0x00010286  eip: 0x9010c456   cs: 0x00000017
       ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
    I left out the "Binary Images Description:" but I can attach or send that if needed, it's quite long.

    Now after building from svn with cmake and making my own .dmg (v0.12) that way I get this in console.log:

    Code:
    2010-01-08 19:03:18.161 DiskImages UI Agent[1901] Could not find image named 'background'.
    /Applications/OBD GPS Logger.app/Contents/MacOS/OBD GPS Logger: line 12: /Applications/OBD GPS Logger.app/Contents/Resources/bin/obdgui: No such file or directory
    /Applications/OBD GPS Logger.app/Contents/MacOS/OBD GPS Logger: line 12: exec: /Applications/OBD GPS Logger.app/Contents/Resources/bin/obdgui: cannot execute: No such file or directory
    Also when initiating cmake before the "make" process I noticed these lines for items not found and seems related:

    Code:
    -- Couldn't find fluid: required for building GUI
    -- Couldn't find fltk: required for building GUI
    Are these packages I'm missing and just need to install somehow? I'm not sure what's wrong with the 0.11 build but the 0.12 build apparently can't make the obdgui and that is the cause of the problem there. Let me know where to go from here and I'll try it out!

    Thanks,
    John

  2. #2
    Newbie
    Join Date
    Jan 2010
    Posts
    6
    I installed fltk with macports and now obdgui builds properly and the program seems to run just fine now. I'll try it out soon.

  3. #3
    SuperMod - OBDII GPS Logger forum
    Auto Apps:loading...

    Join Date
    Mar 2009
    Location
    Los Angeles
    Posts
    924
    Heya,

    My apologies, I was out of town so didn't see this yet. Lemme know if it's working for you! If not, I'm back and paying attention again, now

    Gary (-;
    OBDGPSLogger, for logging OBDII and/or GPS data
    OBDSim, an OBDII/ELM327 software simulator
    mp3car forums: obdgpslogger, obdsim

  4. #4
    Newbie
    Join Date
    Jan 2010
    Posts
    6
    Well no, it doesn't seem to be working so far. When I run from the GUI, I hit Go and it greys out the buttons for a bit and then they come back to normal and nothing happens and no log file is created. Here's a screenshot of the GUI:



    And just to note, the GUI does weird things spatially when resizing, and I think some buttons don't have visible labels because they're squished just above the logfile box:



    I also tried running obdgpslogger from the Terminal and it runs but I see this:

    Code:
    john-lewis-computer:~/obdgpslogger/bin jlewis$ ./obdgpslogger -s /dev/cu.CBT-DevB-1 -d /Users/jlewis/Documents/OBDGPSlogs/echo1.db
    Bus error
    The car is a Toyota Echo and I am using the ElmScan5 Bluetooth device. The device works fine even on this car with OBD Gauge over Bluetooth, I can view DTCs and see live sensor data. As far as I know the ElmScan 5 uses a real ELM327 chip.

    - John L

  5. #5
    SuperMod - OBDII GPS Logger forum
    Auto Apps:loading...

    Join Date
    Mar 2009
    Location
    Los Angeles
    Posts
    924
    Well no, it doesn't seem to be working so far. When I run from the GUI, I hit Go and it greys out the buttons for a bit and then they come back to normal and nothing happens and no log file is created. Here's a screenshot of the GUI:
    The GUI is actually just a wrapper on the command-line application; the behaviour you're seeing is what happens if the command-line application isn't working, or is crashing. Borne out thus:

    I also tried running obdgpslogger from the Terminal and it runs but I see this:
    {stuff}
    Bus Error
    Ugh. Could you by any chance show me a back trace? There's two steps to that; first, build with debug symbols, and second get the backtrace:

    1) Re-run cmake and enable debugging symbols; either use ccmake and change CMAKE_BUILD_TYPE to "Debug", or you can set it on the commandline cmake [building just like you did before, other than the extra parameter]:
    Code:
    cmake -DCMAKE_BUILD_TYPE=Debug ..
    make
    2) Run obdgpslogger from gdb, like this:
    Code:
    john-lewis-computer:~/obdgpslogger/bin jlewis$ gdb ./obdgpslogger
    r -s /dev/cu.CBT-DevB-1 -d /Users/jlewis/Documents/OBDGPSlogs/echo1.db
    The second line is typed at the gdb prompt, and is an 'r' followed by a space and the other command-line options you use. Once the software has crashed, run "bt" at the gdb prompt, and paste the output here.

    And just to note, the GUI does weird things spatially when resizing, and I think some buttons don't have visible labels because they're squished just above the logfile box:
    Yeah, re-writing the GUI to not suck is high on my list of stuff to do. Those buttons above the logfile box are actually part of the FLTK standard filename widget, and make it easier to cut out pieces of the filename/path [you can click on them to see what happens. I don't find it very useful, myself, but it's what's there].

    Thank-you!

    Gary (-;
    OBDGPSLogger, for logging OBDII and/or GPS data
    OBDSim, an OBDII/ELM327 software simulator
    mp3car forums: obdgpslogger, obdsim

  6. #6
    Newbie
    Join Date
    Jan 2010
    Posts
    6
    I don't know if I did this all properly but here's what I got:

    Code:
    (gdb) r -s /dev/cu.CBT-DevB-1 -d /Users/jlewis/Documents/OBDGPSlogs/echo1.db
    Starting program: /Users/jlewis/obdgpslogger/bin/obdgpslogger -s /dev/cu.CBT-DevB-1 -d /Users/jlewis/Documents/OBDGPSlogs/echo1.db
    Reading symbols for shared libraries . done
    
    Program received signal EXC_BAD_ACCESS, Could not access memory.
    Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
    0x90012f53 in strdup ()
    (gdb) bt
    #0  0x90012f53 in strdup ()
    #1  0x00002546 in main (argc=5, argv=0xbffffb58) at /Users/jlewis/obdgpslogger/src/logger/main.c:187

  7. #7
    SuperMod - OBDII GPS Logger forum
    Auto Apps:loading...

    Join Date
    Mar 2009
    Location
    Los Angeles
    Posts
    924
    Hrm. Doesn't look like debugging symbols got built in, but there was enough of a hint to let me find what I think was the problem [getopt's shortopts didn't have a : after the 'd' option [diff]].

    Try an svn update and re-build, hopefully that'll fix it

    Thanks,
    Gary (-;
    OBDGPSLogger, for logging OBDII and/or GPS data
    OBDSim, an OBDII/ELM327 software simulator
    mp3car forums: obdgpslogger, obdsim

  8. #8
    Newbie
    Join Date
    Jan 2010
    Posts
    6
    Code:
    john-lewis-computer:~/obdgpslogger/bin jlewis$ ./obdgpslogger -s /dev/cu.CBT-DevB-1 -d /Users/jlewis/Documents/OBDGPSlogs/echo1.db
    Opening serial port /dev/cu.CBT-DevB-1, this can take a while
    Successfully connected to serial port. Will log obd data
    Creating a new trip


    It made a .db and then I saw that the obdgui is also working now and used the gui to convert to a CSV which converted just fine. Looking forward to testing this while riding around and if I can help with this project let me know.

    Thanks!

    P.S.: Is there a "proper" way to stop a log without just killing the program?

  9. #9
    SuperMod - OBDII GPS Logger forum
    Auto Apps:loading...

    Join Date
    Mar 2009
    Location
    Los Angeles
    Posts
    924
    Great stuff! Seeing people using my stuff [eg, google earth screenshots] gives me the huge huge warm fuzzies, feel free to post screenshots if you get any :-D

    I'm always interested in hearing if you have any questions or suggestions, too!

    Gary (-;
    OBDGPSLogger, for logging OBDII and/or GPS data
    OBDSim, an OBDII/ELM327 software simulator
    mp3car forums: obdgpslogger, obdsim

  10. #10
    Newbie
    Join Date
    Jan 2010
    Posts
    6
    Well I don't have GPS capabilities but the OBD logging alone is great. Maybe I'll add GPS in the future.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •