From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22111 invoked by alias); 16 Jun 2008 01:09:02 -0000 Received: (qmail 22102 invoked by uid 22791); 16 Jun 2008 01:09:01 -0000 X-Spam-Check-By: sourceware.org Received: from vms046pub.verizon.net (HELO vms046pub.verizon.net) (206.46.252.46) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 16 Jun 2008 01:08:42 +0000 Received: from ultsol.com ([72.93.239.216]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K2J0065L76FT4O1@vms046.mailsrvcs.net> for gdb@sourceware.org; Sun, 15 Jun 2008 20:08:40 -0500 (CDT) Date: Mon, 16 Jun 2008 01:09:00 -0000 From: "Fahd Abidi" Subject: RE: What do I need to look at the source while debugging? To: "Igor Korot" , "Michael Snyder" Cc: Message-id: <071DB0C788671B48940BC79F8B49306934E39B@ultsol01.tewks.ultsol.local> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable Content-class: urn:content-classes:message X-Ninja-PIM: Scanned by Ninja X-Ninja-AttachmentFiltering: (no action) 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: 2008-06/txt/msg00155.txt.bz2 First make sure that your program file (SQLDriverConnectW.o) is build with debug symbols. to accomplish this make sure you pass the "-g" flag into gdb. Then open gdb with the following arguments: linux# gdb SQLDriverConnectW.o You will need to attach this gdb session to a gdbserver to begin the debugging. So start your application with the following commands: linux# gdbserver SQLDriverConnectW.o I forget the exact command to give to gdbserver to specify what port you will use to connect. Next from gdb connect to the gdbserver: (gdb) target remote ****your connection settings**** Fahd Abidi -----Original Message----- From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf Of Igor Korot Sent: Sunday, June 15, 2008 12:30 AM To: Michael Snyder Cc: gdb@sourceware.org Subject: Re: What do I need to look at the source while debugging? Hi, I just tried to use a 'load' command: (gdb) load /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/DriverMan ager/SQLDriverConnectW.c `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. You can't do that when your target is `multi-thread' What does this mean? I just used KDdevelop to create a project... and simply trying: (gdb) break /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/DriverMan ager/SQLDriverConnect.c:616 No source file named /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/DriverMan ager/SQLDriverConnect.c. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 2 (/home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/DriverMa nager/SQLDriverConnect.c:616) pending. However the file exists and I have a reading permission... Thank you. -----Original Message----- >From: Michael Snyder >Sent: Jun 11, 2008 2:44 PM >To: Igor Korot >Cc: gdb@sourceware.org >Subject: Re: What do I need to look at the source while debugging? > >On Wed, 2008-06-11 at 10:53 -0700, Igor Korot wrote: > >> >If not, you can override gdb's source file search path by using the=20 >> >"dir" command (see "help dir") >>=20 >> You mean like this: >>=20 >> gdb myprogram >> gdb> dir=20 >> gdb> /home/igor/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/D >> gdb> rivers >>=20 >> right? > >Right. > >