[odb-users] odb compiler crashes when using --options-file in Mac Os X 10.9.5

[Alexandre Pretyman]

Just a note: I put the spaces inside the options file, the odb compiler
does not crash, however it doesn't pick up the include directories either.

On 14 August 2015 at 14:18, Alexandre Pretyman <alexandre.pretyman at gmail.com
> wrote:

> Hi Boris,
>
> As suggested, I ran the compiler under lldb and printed the backtrace
> after the SIGABORT, and you seem to be right as to it is a problem in the
> exception handling:
>
> Process 794 stopped
> * thread #1: tid = 0x37ca, 0x00007fff8bb99866
> libsystem_kernel.dylib`__pthread_kill + 10, queue =
> 'com.apple.main-thread', stop reason = signal SIGABRT
>     frame #0: 0x00007fff8bb99866 libsystem_kernel.dylib`__pthread_kill + 10
> libsystem_kernel.dylib`__pthread_kill + 10:
> -> 0x7fff8bb99866:  jae    0x7fff8bb99870            ; __pthread_kill + 20
>    0x7fff8bb99868:  movq   %rax, %rdi
>    0x7fff8bb9986b:  jmp    0x7fff8bb96175            ; cerror_nocancel
>    0x7fff8bb99870:  retq
> (lldb) bt
> * thread #1: tid = 0x37ca, 0x00007fff8bb99866
> libsystem_kernel.dylib`__pthread_kill + 10, queue =
> 'com.apple.main-thread', stop reason = signal SIGABRT
>   * frame #0: 0x00007fff8bb99866 libsystem_kernel.dylib`__pthread_kill + 10
>     frame #1: 0x00007fff8f4cb35c libsystem_pthread.dylib`pthread_kill + 92
>     frame #2: 0x00007fff92e69b1a libsystem_c.dylib`abort + 125
>     frame #3: 0x00000001000178d6 odb`uw_init_context_1 + 134
>     frame #4: 0x0000000100017e0e odb`_Unwind_RaiseException + 62
>     frame #5: 0x0000000100010d2b odb`__cxa_throw + 91
>     frame #6: 0x00000001000261b1 odb`options::_parse(cli::scanner&,
> cli::unknown_mode, cli::unknown_mode) + 481
>     frame #7: 0x0000000100038a91 odb`options::options(cli::scanner&,
> cli::unknown_mode, cli::unknown_mode) + 4401
>     frame #8: 0x00000001000b16b0 odb`main + 7408
>     frame #9: 0x00000001000196e4 odb`start + 52
>
>
> However I don't know how to interpret these messages, would you be kind
> enough to drop a few words on why this would happen?
>
> Putting the spaces in between the options and option value seemed to have
> solved the problem compiling odb, thanks for the tip. It was not clear from
> the odb manual that they had to be separated, or maybe I'm just stupid....
>
> Thank you!
>
>
>
> On 14 August 2015 at 12:45, Boris Kolpackov <boris at codesynthesis.com>
> wrote:
>
>> Hi Alexandre,
>>
>> Alexandre Pretyman <alexandre.pretyman at gmail.com> writes:
>>
>> > I am using odb compiler with the --options-file flag to add additional
>> > flags to the compilation in MacOS 10.9.5, however it crashes with "Abort
>> > trap: 6". If I take these flags and put them in the command line
>> itself, it
>> > works normally.
>>
>> I tried your command line/options file and I get this error:
>>
>> unknown option
>> '-I/Users/discipline/Documents/Projects/StudyBuddy/generated-odb'
>>
>> Looking inside your options file I see that you are using the -I/foo
>> format rather than -I /foo. Currently, inside option files, ODB can
>> only handle -I /foo (and -D foo). After changing this, I was able
>> to run your command line on a test file without any errors.
>>
>> Of courser the question that goes unanswered is why you get SIGABRT
>> instead of the error message like I do. My only idea is that the
>> exception handling is not working in ODB on your Mac OS version for
>> some reason (wouldn't be surprised at all; these days Mac OS is worse
>> than Windows). Any chance you could run that command line under the
>> debugger and get a stack trace?
>>
>> Boris
>>
>
>
>
> --
> Alexandre Pretyman
>



-- 
Alexandre Pretyman