This is the mail archive of the gdb@sources.redhat.com 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: Debug code in data section in gdb

From: Andreas Schwab <schwab at suse dot de>
To: Tao Zhang <zhangtao at cc dot gatech dot edu>
Cc: Michael Elizabeth Chastain <mec dot gnu at mindspring dot com>,gdb at sources dot redhat dot com
Date: Tue, 22 Jun 2004 22:43:22 +0200
Subject: Re: Debug code in data section in gdb
References: <20040622181936.BF6E14B104@berman.michael-chastain.com><Pine.GSO.4.58.0406221509070.26734@gaia.cc.gatech.edu>

Tao Zhang <zhangtao@cc.gatech.edu> writes:

> Hi, Michael
>
> I tried that many times, it doesn't work for me. I even played some trick
> so that the code buffer is actually placed in code section now. It still
> doesn't work. I am very confused. The breakpoints work just fine for other
> code.

Please define "doesn't work".  What are the symptoms?

> So break *0x12344657 should work?

Yes.  GDB does not distinguish between "code" and "data" section when
placing a breakpoint, it's all just memory.

Andreas.

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

Follow-Ups:
- Re: Debug code in data section in gdb
  - From: Tao Zhang

References:
- Re: Debug code in data section in gdb
  - From: Michael Elizabeth Chastain
- Re: Debug code in data section in gdb
  - From: Tao Zhang

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