Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

TDS3 Debuger ?

2 views
Skip to first unread message

Udo Karlins

unread,
Sep 25, 1995, 3:00:00 AM9/25/95
to
Hi !

I've a problem with the TDS3 Debuger. In the debugsession he tells me
"Error: Debug info too large (ix.tags is full)"

Any idea ??

Thanks Udo

--
| Udo Karlins | WMD-GmbH | Gesellschaft fuer |
| Tel : ++49 40 - 589 58 124 | Vogt-Cordes-Damm 10 | _W_issenschaftliche |
| Fax : ++49 40 - 589 58 199 | 22453 Hamburg | _M_essgeraete und |
| Email: kar...@wmd.de | Germany | _D_atenerfassung mbH |

ROEBBERS_HW

unread,
Sep 26, 1995, 3:00:00 AM9/26/95
to
Udo Karlins (kar...@wmdhh.wmd.de) wrote:
: Hi !

Hi,

: I've a problem with the TDS3 Debuger. In the debugsession he tells me


: "Error: Debug info too large (ix.tags is full)"

: Any idea ??

I think you're running out of memory on the root transputer. The debugger runs
on the root transputer, and determines from the environment variable IDEBUGSIZE
(or something to that effect) the amount of memory on the root transputer.
From this it calculates the amount of free memory space. It divides this
amount into chunks for use by various parts of the debugger.
It seems to run out of space for the array where the debug tags are stored.
You might remedy this by compiling modules that you don't want to debug
without debugging information, so as to reduce the amount of debugging
information.
Your best bet is probably (if you can) to use a root transputer with more
memory and to adapt IDEBUGSIZE and IMEMSIZE accordingly.

Alternatively you can get the debugger source from hensa.unix.ac.uk and
change the way memory is allocated so that it might work for you.
This could be overkill though!

Hope this helps,

: Thanks Udo

Herman Roebbers
Philips TASS / Philips Medical Systems

0 new messages