idb core dumps - idbc weird warnings - idbc cant catch my break points.

[rusty0412]

Hi,

I am opening idb and it cores after start up. Also, idbc gives all of these warnings when I start it with and without any arguments. Furthermore, idbc fails to be able to catch break points in my code. It can catch break points in calls to glibc just fine but cannot provide a backtrace. I am compiling with g++ 4.1.2 20080704 (Red Hat 4.1.2-48) in RHEL 5.6.

I tried running idb under JRE 1.5.0_06-b05 and 1.6.0_16-b01.

Both are Version 12.0, Build [1.3842.2.129]

Thanks

IDB backtrace:

(gdb) backtrace full

#0 0x00002ac2a01ab541 in xercesc_2_8::ValueStackOf<:DOMNODE>::~ValueStackOf ()

from /intel/studio_xe/composerxe-2011.0.084/debugger/lib/intel64/libxerces-c.so.28

No symbol table info available.

#1 0xc4d0000000000b8e in ?? ()

No symbol table info available.

#2 0xd23200007fff3ede in ?? ()

No symbol table info available.

#3 0x68b000002ac2a02d in ?? ()

No symbol table info available.

#4 0xb67a000000000b8e in ?? ()

No symbol table info available.

#5 0xca6000002ac29ff2 in ?? ()

No symbol table info available.

#6 0xb3d9000000000b8d in ?? ()

No symbol table info available.

#7 0x000000002ac29ff2 in ?? ()

No symbol table info available.

#8 0x0000000000000000 in ?? ()

No symbol table info available.

(gdb)

IDBC weird errors:

host01:/home/myuser/bin $ /intel/studio_xe/compilerpro-12.0.0.084/bin/intel64/idbc

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

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

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

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

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

No symbol "m" in current context.

Cannot evaluate '$tree = m'.

user defined function may only have 10 arguments.

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

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

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

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

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

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

No symbol "v" in current context.

No symbol "v" in current context.

Cannot evaluate '$size = v._M_impl._M_finish - v._M_impl._M_start'.

Vector size = 0

Vector capacity = 0

Element No symbol "v" in current context.

No symbol "v" in current context.

No symbol "v" in current context.

Cannot evaluate '$size = v._M_impl._M_finish - v._M_impl._M_start'.

Vector size = 0

Vector capacity = 0

Element No symbol "v" in current context.

user defined function may only have 10 arguments.

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

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

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

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

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

No symbol "l" in current context.

Cannot evaluate '$head = &l._M_impl._M_node'.

No symbol "l" in current context.

Cannot evaluate '$head = &l._M_impl._M_node'.

user defined function may only have 10 arguments.

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

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

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

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

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

No symbol "l" in current context.

Cannot evaluate '$head = &l._M_impl._M_node'.

user defined function may only have 10 arguments.

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

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

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

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

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

No symbol "m" in current context.

Cannot evaluate '$tree = m'.

No symbol "m" in current context.

Cannot evaluate '$tree = m'.

user defined function may only have 10 arguments.

user defined function may only have 10 arguments.

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

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

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

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

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

No symbol "m" in current context.

Cannot evaluate '$tree = m'.

user defined function may only have 10 arguments.

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

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

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

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

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

No symbol "s" in current context.

Cannot evaluate '$tree = s'.

user defined function may only have 10 arguments.

user defined function may only have 10 arguments.

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

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

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

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

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

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

No symbol "d" in current context.

Cannot evaluate '$start_cur = d._M_impl._M_start._M_cur'.

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

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

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

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

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

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

No symbol "s" in current context.

Cannot evaluate '$start_cur = s.c._M_impl._M_start._M_cur'.

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

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

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

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

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

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

No symbol "q" in current context.

Cannot evaluate '$start_cur = q.c._M_impl._M_start._M_cur'.

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

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

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

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

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

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

No symbol "pq" in current context.

No symbol "pq" in current context.

Cannot evaluate '$size = pq.c._M_impl._M_finish - pq.c._M_impl._M_start'.

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

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

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

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

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

No symbol "b" in current context.

Cannot evaluate 'b._M_w'.

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

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

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

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

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

user defined function may only have 10 arguments.

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

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

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

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

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

user defined function may only have 10 arguments.

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

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

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

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

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

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

Intel Debugger for applications running on Intel 64, Version 12.0, Build [1.3842.2.129]

(idb)

[Hubert_H_Intel]

It looks like this is a problem with the shell that cannot run the idb|idbc script correctly. Which is your shell (echo $0)? How did you source the compiler/debugger tools? It should done with running (default):
/opt/intel/bin/compilervars.sh|csh prior to use of the debugger.
Hubert.

[Georg_Z_Intel]

Hi,

in addition to Hubert's question could you please also check whether there's an init file (i.e. $HOME/.gdbinit). If you only start IDB via the provided "idbc" script, and not specifying more paramenters, the parser errors likely result from such an init file. IDB will behave the same way as GDB and execute it as first step after startup. However, IDB might not recognize some commands in this file and print "Unable to parse input as legal command or C expression." errors instead.

Thank you,

Georg