idb getting bug with Mac 10.5.6

forcpp · ‎06-25-2009

I recently noticed the idb coming with 10.1.015 (icc/ifort) giving bug with Mac 10.5.6. When I prompt

riki@host$ idb

we are getting

line: 137 Unable to parse input as legal command or C expression.

Output radix now set to decimal 16, hex 10, octal 20.

line: 141 Unable to parse input as legal command or C expression.

line: 148 Unable to parse input as legal command or C expression.

.

line: 675 Unable to parse input as legal command or C expression.

Intel Debugger for applications running on Intel 64, Version 35, Build 20080310

\033[31mgdb$ \033[0m

Any clue about this bug ?

forcpp · ‎06-25-2009

Quoting - forcpp

I recently noticed the idb coming with 10.1.015 (icc/ifort) giving bug with Mac 10.5.6. When I prompt

riki@host$ idb

we are getting

line: 137 Unable to parse input as legal command or C expression.

Output radix now set to decimal 16, hex 10, octal 20.

line: 141 Unable to parse input as legal command or C expression.

line: 148 Unable to parse input as legal command or C expression.

.

.

.

.

line: 675 Unable to parse input as legal command or C expression.

Intel Debugger for applications running on Intel 64, Version 35, Build 20080310

�33[31mgdb$ �33[0m

Any clue about this bug ?

I got the reason behind it. It is not the bug of intel compilers nor mac. It is due to .gdbinit file which I added. By the way how can we delete a post if accidently wrong discussion is posted.

Steven_L_Intel1 · ‎06-25-2009

You can ask a moderator to delete it, but in most cases we'd prefer to leave the discussion there as someone else might run into the same issue in the future.