LINK : error : Internal error during ReadSymbolTable
Brian Toothill
LINK : error : Internal error during ReadSymbolTable
during linking an OCX. Also, the ActiveX control test container crashes
when I insert the above control.
Tian Min Huang
Based on my experience, this link error may appear when an .obj exceeds
32767 (0x7fff) sections in Visual C++ 6.0. In VC7, we have upped the limit
to be basically an unsigned short instead, giving us a 0xfeff limit instead
of 0x7fff. Section indices of 0xff00 through 0xffff are still "special."
If you are using VC6, you will need do one or more of the following tasks
in order to work around it:
1. break apart the source file into smaller pieces
2. don't compiler /Gy
3. don't use /Gf or /GF
4. use fewer inline functions (instantiate them in different compilands).
If the problem persists, could you post a simple project which is able to
reproduce the problem?
I am standing by for your response.
Have a nice day!
Regards,
HuangTM
Microsoft Online Partner Support
MCSE/MCSD
Get Secure! – www.microsoft.com/security
This posting is provided “as is” with no warranties and confers no rights.
Peter Stark
May I chime in at this point, as I've got a similar problem. I'm
generating a rather large ActiveX Wrapper DLL using templates, which
has worked fine in the past.
After the addition of a new class, I now encounter problems during the
link process with debug information. Generating the RELEASE product
seems to work fine.
The encountered error message is "Internal error during
ReadSymbolTable". If I remove some existing classes from the
interface, the project will link ok.
It seems to me, that all templates are instantiated within
BEGIN_OBJECT_MAP()/END_OBJECTMAP(), thus busting some linker
limitation. Is there any way to
- increase the linker resources
- or split up the object map into seperate modules
or any other solution, that preserves the external DLL interface ?
I'm working with WindowsXP SP1 and VS6 Prof.
Thanx for your support...
Peter
Yan-Hong Huang[MSFT]
Thanks for posting in the group.
Have you build it in VC 7 to see if the probelm is still there? Also,
please rebuild the whole project and test again.
Best regards,
Yanhong Huang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
!From: peter...@barco.com (Peter Stark)
!Newsgroups: microsoft.public.vc.mfc
!Subject: Re: LINK : error : Internal error during ReadSymbolTable
!Date: 17 Sep 2003 04:22:29 -0700
!Organization: http://groups.google.com/
!Lines: 54
!Message-ID: <4553abc9.0309...@posting.google.com>
!References: <OcXUBNJc...@TK2MSFTNGP12.phx.gbl>
<axpB04R...@cpmsftngxa06.phx.gbl>
!NNTP-Posting-Host: 194.7.240.2
!Content-Type: text/plain; charset=ISO-8859-1
!Content-Transfer-Encoding: 8bit
!X-Trace: posting.google.com 1063797750 22073 127.0.0.1 (17 Sep 2003
11:22:30 GMT)
!X-Complaints-To: groups...@google.com
!NNTP-Posting-Date: 17 Sep 2003 11:22:30 GMT
!Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!news-out.cwix.com!newsfeed.cwix.co
m!newspeer.monmouth.com!newshosting.com!news-xfer1.atl.newshosting.com!sn-xi
t-03!sn-xit-06!sn-xit-08!sn-xit-09!supernews.com!postnews1.google.com!not-fo
r-mail
!Xref: cpmsftngxa06.phx.gbl microsoft.public.vc.mfc:390929
!X-Tomcat-NG: microsoft.public.vc.mfc
!
!timh...@online.microsoft.com (Tian Min Huang) wrote in message
news:<axpB04R...@cpmsftngxa06.phx.gbl>...
!> Hi Brian,
!>
!> Based on my experience, this link error may appear when an .obj exceeds
!> 32767 (0x7fff) sections in Visual C++ 6.0. In VC7, we have upped the
limit
!> to be basically an unsigned short instead, giving us a 0xfeff limit
instead
!> of 0x7fff. Section indices of 0xff00 through 0xffff are still "special."
!>
!> If you are using VC6, you will need do one or more of the following
tasks
!> in order to work around it:
!> 1. break apart the source file into smaller pieces
!> 2. don't compiler /Gy
!> 3. don't use /Gf or /GF
!> 4. use fewer inline functions (instantiate them in different compilands).
!>
!> If the problem persists, could you post a simple project which is able
to
!> reproduce the problem?
!>
!> I am standing by for your response.
!>
!> Have a nice day!
!>
!> Regards,
!>
!> HuangTM
!> Microsoft Online Partner Support
!> MCSE/MCSD
!>
!> Get Secure! – www.microsoft.com/security
!> This posting is provided “as is” with no warranties and confers no
rights.
!
!May I chime in at this point, as I've got a similar problem. I'm
!generating a rather large ActiveX Wrapper DLL using templates, which
!has worked fine in the past.
!
!After the addition of a new class, I now encounter problems during the
!link process with debug information. Generating the RELEASE product
!seems to work fine.
!
!The encountered error message is "Internal error during
!ReadSymbolTable". If I remove some existing classes from the
!interface, the project will link ok.
!
!It seems to me, that all templates are instantiated within
!BEGIN_OBJECT_MAP()/END_OBJECTMAP(), thus busting some linker
!limitation. Is there any way to
! - increase the linker resources
! - or split up the object map into seperate modules
!or any other solution, that preserves the external DLL interface ?
!
!I'm working with WindowsXP SP1 and VS6 Prof.
!
!Thanx for your support...
!Peter
!