delorie.com/archives/browse.cgi | search |
Date: | Mon, 22 May 2000 09:42:46 +0300 (IDT) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | Leon Zadorin <Leon AT caresystems DOT com DOT au> |
cc: | mingw32 AT egroups DOT com, djgpp AT delorie DOT com |
Subject: | Re: debug information for custom string classes |
In-Reply-To: | <51FF8E06B654D111B9CA0000E8D863B4096E0E@www.caresystems.com.au> |
Message-ID: | <Pine.SUN.3.91.1000522094203.22890N-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Mon, 22 May 2000, Leon Zadorin wrote: > now if at some point i break in gdb and want to have a look at the > variables data - it is ieasy for int ie > p variableName > but the same p command will not provide the contents of a string (since > it is made from linked list of characters) You should be able to use the GDB user-defined command feature to write a special command that will print your linked list by chasing the next pointer. The GDB manual describes how to write your own commands.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |