User forums > Nightly builds

The 09 October 2010 build (6688) DEBUGGER BRANCH version is out.

<< < (4/5) > >>

oBFusCATed:
I guess that the paths stored in the debug info are wrong.
Please verify they are correct (I don't know how, sorry).

How are you building the CryptoPP lib?

Zadirion:

--- Quote from: oBFusCATed on October 25, 2010, 02:02:18 pm ---How are you building the CryptoPP lib?

--- End quote ---
The CryptoPP source files are directly included in the project. I'm not building CryptoPP as a separate library.


--- Quote ---I guess that the paths stored in the debug info are wrong.
Please verify they are correct (I don't know how, sorry).

--- End quote ---
Well, the bummer is I don't know how either. Like you, I suspect wrong paths might be the reason this is failing.

oBFusCATed:
Can you try different GCC and GDB (try several combinations)?
Can you give as the build log or a simple test project + sources.

I've made a little observation using variaous reports in the forum:
1. gcc 4.5.x causes problems with debugging (gdb 7.2 might work, I don't know for sure).
2. gdb works better in linux, the windows version is less stable.

mushakk:
Hi!

First say I love this branch. Are there some news?

I know maybe this is not the correct forum but I want to launch a proposal: When we add a pointer to the watches window I think will be better display the pointer address (like now) and have a + symbol to inspect the contents of the variable like if we had typed '*pointer'. This is the behavior of Visual Studio debugger that I think is more productive for the developer.

Thanks for your work and sorry about the intrusion.

oBFusCATed:
Can't be done (easily/reliably) with the current implementation.
There is a gdb/mi plugin in the works that does it already,
unfortunately I don't have much time to work on it at the moment.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version