This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: debugging stripped binary/library & coredump without binary

From: Andreas Schwab <schwab at suse dot de>
To: "Sudhakar G" <list dot sudhakar at gmail dot com>
Cc: gdb at sourceware dot org
Date: Wed, 13 Jun 2007 11:26:05 +0200
Subject: Re: debugging stripped binary/library & coredump without binary
References: <ce31d420706120352yc7fbd18h4585cb695af72525@mail.gmail.com> <20070612112359.GD29495@caradoc.them.org> <ce31d420706130206o5d0ab18bwd7a4581a8118f458@mail.gmail.com>

"Sudhakar G" <list.sudhakar@gmail.com> writes:

> Thanks Daniel. But I want to know how to debug once core file is
> opened without access to program file but with access only to source
> code. Are there any tips?

You need at least the debugging symbols in order to do source level
debugging.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- debugging stripped binary/library & coredump without binary
  - From: Sudhakar G
- Re: debugging stripped binary/library & coredump without binary
  - From: Daniel Jacobowitz
- Re: debugging stripped binary/library & coredump without binary
  - From: Sudhakar G

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]