User forums > Help

debugger_gdbmi will not run CB

<< < (5/6) > >>

oBFusCATed:
I guess it is in the $PATH :)

Pecan:

--- Quote from: oBFusCATed on April 07, 2012, 10:47:29 pm ---I guess it is in the $PATH :)

--- End quote ---

No, it's not in the path, and it wasn't the problem. I uninstalled it and debugger_gdbmi still exists the same way.

At this point, I'm at a lose as to what to do. If I can't debug CB, it's a deal breaker.

I think I'll try to find a way to to get debugger_gdbmi to ignore the return codes from those library loads and see what happens.

oBFusCATed:
Can you try what happens if you comment this line: wxSetEnv(CB_LIBRARY_ENVVAR, newLibPath); in plugin.cpp?

Pecan:

--- Quote from: oBFusCATed on April 07, 2012, 11:46:13 pm ---Can you try what happens if you comment this line: wxSetEnv(CB_LIBRARY_ENVVAR, newLibPath); in plugin.cpp?

--- End quote ---

Same thing. No change.

--- Code: ---[debug]notification event recieved!
[debug]output==>=thread-exited,id="1",group-id="i1"
[debug]output==>=thread-group-exited,id="i1",exit-code="01777777777777777777777"
[debug]output==>*stopped,reason="exited",exit-code="037777777777"
[debug]unparsable_output==>(gdb)
[debug]notification event recieved!
[debug]notification event recieved!
[debug]notification event recieved!
[debug]cmd==>00000000000-gdb-exit
[debug]GDBExecutor is not stopped, but command (-gdb-exit) was executed!
[debug]output==>00000000000^exit


--- End code ---

oBFusCATed:
Are you still using the python pretty printers?
Can you try to remove the two source commands?

Navigation

[0] Message Index

[#] Next page

[*] Previous page