Hello,

We're using Codegear C++ Builder 2007, our project group has 8 library packages, 6 regular installable packages (with components), and 3 applications.

I'm trying to debug an exception which occurs in one of the library. The debugger breaks just fine, on the correct line, however none of the symbols are defined with the debugger. Placing a breakpoint in the same class results in the same problem, in fact, the this pointer isn't even being translated to the correct symbol, and casting it to the class doesn't work either (E2451 Undefined symbol 'TDXDisplayControl'). Ironically that's on top of the stack (which displays it just fine).

For some bizarre reason only the symbols from a specific CPP file are 'lost'. Unfortunately this is exactly the class that I need to debug.

Could someone come up with a checklist? "Debug Information" & "Debug Line Information" are both enabled in the C++ Compiler settings. The linker also links "Full debug information".

Cheers,
Onno

John Grabner wrote:

>This is long standing bug. I have had it with both BCB6 and Bds2006. 

I don't suppose you can create a demo project, but if you can give me
any info that would help me to reproduce it I'll do my best to do so
and get it opened. I've seen the debugger flake out and not show info
that it should, but the problem always seems to be fleeting - next
debug session everything works.

 - Leo

Yeah, I didnt' see it on QC either so I've filed a bug:
http://qc.codegear.com/wc/qcmain.aspx?d=56804

Unfortunately we cannot offer a code sample (as in, it doesn't happen in a 
small test project, and we arent' keen on sending our entire codebase. It's 
rather sensitive).

--Onno

"John Grabner"  wrote in message 
news:4786a260$1@newsgroups.borland.com...
> OnnoJ wrote:
>> Hello,
>>
>> We're using Codegear C++ Builder 2007, our project group has 8 library 
>> packages, 6 regular installable packages (with components), and 3 
>> applications.
>>
>> I'm trying to debug an exception which occurs in one of the library. The 
>> debugger breaks just fine, on the correct line, however none of the 
>> symbols are defined with the debugger. Placing a breakpoint in the same 
>> class results in the same problem, in fact, the this pointer isn't even 
>> being translated to the correct symbol, and casting it to the class 
>> doesn't work either (E2451 Undefined symbol 'TDXDisplayControl'). 
>> Ironically that's on top of the stack (which displays it just fine).
>>
>> For some bizarre reason only the symbols from a specific CPP file are 
>> 'lost'. Unfortunately this is exactly the class that I need to debug.
>>
>> Could someone come up with a checklist? "Debug Information" & "Debug Line 
>> Information" are both enabled in the C++ Compiler settings. The linker 
>> also links "Full debug information".
>>
>> Cheers,
>> Onno
> This is long standing bug. I have had it with both BCB6 and Bds2006. 
> CodeGear is aware of it although I do not think it has a QC number.
>
> John. 

OnnoJ wrote:
> Hello,
> 
> We're using Codegear C++ Builder 2007, our project group has 8 library packages, 6 regular installable packages (with components), and 3 applications.
> 
> I'm trying to debug an exception which occurs in one of the library. The debugger breaks just fine, on the correct line, however none of the symbols are defined with the debugger. Placing a breakpoint in the same class results in the same problem, in fact, the this pointer isn't even being translated to the correct symbol, and casting it to the class doesn't work either (E2451 Undefined symbol 'TDXDisplayControl'). Ironically that's on top of the stack (which displays it just fine).
> 
> For some bizarre reason only the symbols from a specific CPP file are 'lost'. Unfortunately this is exactly the class that I need to debug.
> 
> Could someone come up with a checklist? "Debug Information" & "Debug Line Information" are both enabled in the C++ Compiler settings. The linker also links "Full debug information".
> 
> Cheers,
> Onno
This is long standing bug. I have had it with both BCB6 and Bds2006. 
CodeGear is aware of it although I do not think it has a QC number.

John.

Hi Bob,

Thanks for your reply.
Local options don't differ from the project's options, and the project's 
options are not different from the other projects.

I'll try there.

--Onno

"Bob Gonder"  wrote in message 
news:7ur9o35jk66fur6lvmqugidn6jrqbojuk1@4ax.com...
> OnnoJ wrote:
>
>>>For some bizarre reason only the symbols from a specific CPP file are 
>>>'lost'.
>
> Check the local options for that module.
> Debuging is probably turned off for that one.
>
>>I hope that I posted this in the correct newsgroup
>
> Not really.
> This group is about the C/C++ Languages.
> Your question is more about the IDE.
>
> 

OnnoJ wrote:

>>For some bizarre reason only the symbols from a specific CPP file are 'lost'.

Check the local options for that module.
Debuging is probably turned off for that one.

>I hope that I posted this in the correct newsgroup

Not really.
This group is about the C/C++ Languages.
Your question is more about the IDE.

In addition, it seems to mistake some types for void.
"((TEObject*)pE) E2468 Value of type void is not allowed"

TEObject is declared as:
   class EXPORTPK TEObject
       |--> expands to: class __declspec(package) TEObject

But has been foreward declared as:
    class TEObject;

Does anyone know what's going on here?
What does Builder use for retrieving the symbols in debugging, its TDS file? 
Any way to inspect/browse/dump that?

Kind regards,
--Onno

"OnnoJ"  wrote in message 
news:4784e68b$1@newsgroups.borland.com...
>
> "OnnoJ"  wrote:
>>
>>Hello,
>>
>>We're using Codegear C++ Builder 2007, our project group has 8 library 
>>packages, 6 regular installable packages (with components), and 3 
>>applications.
>>
>>I'm trying to debug an exception which occurs in one of the library. The 
>>debugger breaks just fine, on the correct line, however none of the 
>>symbols are defined with the debugger. Placing a breakpoint in the same 
>>class results in the same problem, in fact, the this pointer isn't even 
>>being translated to the correct symbol, and casting it to the class 
>>doesn't work either (E2451 Undefined symbol 'TDXDisplayControl'). 
>>Ironically that's on top of the stack (which displays it just fine).
>>
>>For some bizarre reason only the symbols from a specific CPP file are 
>>'lost'. Unfortunately this is exactly the class that I need to debug.
>>
>>Could someone come up with a checklist? "Debug Information" & "Debug Line 
>>Information" are both enabled in the C++ Compiler settings. The linker 
>>also links "Full debug information".
>>
>>Cheers,
>>Onno
>
> I hope that I posted this in the correct newsgroup, I didn't see a 
> borland.public.cppbuilder.debugging group :-( 

"OnnoJ"  wrote:
>
>Hello,
>
>We're using Codegear C++ Builder 2007, our project group has 8 library packages, 6 regular installable packages (with components), and 3 applications.
>
>I'm trying to debug an exception which occurs in one of the library. The debugger breaks just fine, on the correct line, however none of the symbols are defined with the debugger. Placing a breakpoint in the same class results in the same problem, in fact, the this pointer isn't even being translated to the correct symbol, and casting it to the class doesn't work either (E2451 Undefined symbol 'TDXDisplayControl'). Ironically that's on top of the stack (which displays it just fine).
>
>For some bizarre reason only the symbols from a specific CPP file are 'lost'. Unfortunately this is exactly the class that I need to debug.
>
>Could someone come up with a checklist? "Debug Information" & "Debug Line Information" are both enabled in the C++ Compiler settings. The linker also links "Full debug information".
>
>Cheers,
>Onno

I hope that I posted this in the correct newsgroup, I didn't see a borland.public.cppbuilder.debugging group :-(