From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15119 invoked by alias); 29 Apr 2011 18:36:55 -0000 Received: (qmail 15029 invoked by uid 22791); 29 Apr 2011 18:36:53 -0000 X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from seraph.oankali.net (HELO seraph.oankali.net) (209.9.237.222) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 29 Apr 2011 18:36:39 +0000 Received: from seraph.oankali.net (seraph.oankali.net [209.9.237.222]) (authenticated bits=0) by seraph.oankali.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p3TIaas8013430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 29 Apr 2011 14:36:37 -0400 Date: Fri, 29 Apr 2011 18:36:00 -0000 From: Richard Silverman To: GDB Mailing List Subject: teaching gdb about new types? Message-ID: User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-04/txt/msg00167.txt.bz2 Hello, This seems as if it should be simple, but I can't find an answer. I would like to teach gdb about new types relevant to the program being debugged, which are not among the debugging info in the program. A concrete example: I have a program which uses pthreads from libc. It calls: int pthread_cond_wait(pthread_cond_t *restrict cond, pthread_mutex_t *restrict mutex); ... and the argument types are defined in system header files. But libc.so has no debugging info, so gdb doesn't know about these types, and can't interpret the arguments for me. How can I teach gdb about these types? Thanks, - Richard