At 10:54 AM -0700 5/27/02, David O'Brien wrote:
>Verify that your entire kernel is built with "-g -gstabs+". If you still
>cannot use gdb on a core dump, maybe there is a core dump format change
>GDB needs to catch up with. Please use the various objdump, etc. tools
>to verify what type of debug
On Mon, May 27, 2002 at 04:08:44PM +0900, Jun Kuriyama wrote:
> At Mon, 27 May 2002 02:46:01 + (UTC),
> David O'Brien wrote:
> > Add it to COPTFLAGS. Why are you adding it to DEBUG?
> > ``grep DEBUG /sys/conf/*.mk /sys/conf/Makefile.*'' shows DEBUG is not
> > used this way.
>
> I added it to
At Mon, 27 May 2002 02:46:01 + (UTC),
David O'Brien wrote:
> Add it to COPTFLAGS. Why are you adding it to DEBUG?
> ``grep DEBUG /sys/conf/*.mk /sys/conf/Makefile.*'' shows DEBUG is not
> used this way.
I added it to DEBUG because I think "-gstabs+" will be used as
replacement of "-g". I ad
On Mon, May 27, 2002 at 11:12:47AM +0900, Jun Kuriyama wrote:
> At Wed, 22 May 2002 18:54:02 + (UTC),
> David O'Brien wrote:
> > -ggdb means to use the most "expressive" debugging format the compiler
> > knows about. You want -gstabs+ or -gstabs
>
> I cannot debug a kernel with -gstabs+ opti
At Sun, 26 May 2002 21:35:28 -0500,
David W. Chapman Jr. <[EMAIL PROTECTED]> wrote:
> > % sudo gdb52
> Last time I checked, gdb was broken in -current and people were
> encouraged to use gdb in the ports system, but this may be oudated.
Yes, I'm using gdb52 from ports/devel/gdb52.
--
Jun Kur
On Mon, May 27, 2002 at 11:12:47AM +0900, Jun Kuriyama wrote:
> At Wed, 22 May 2002 18:54:02 + (UTC),
> David O'Brien wrote:
> > -ggdb means to use the most "expressive" debugging format the compiler
> > knows about. You want -gstabs+ or -gstabs
>
> I cannot debug a kernel with -gstabs+ opti
At Wed, 22 May 2002 18:54:02 + (UTC),
David O'Brien wrote:
> -ggdb means to use the most "expressive" debugging format the compiler
> knows about. You want -gstabs+ or -gstabs
I cannot debug a kernel with -gstabs+ option. Any hints about this?
% cd sys/i386/compile/WATERBLUE
% grep gdb ../
On Wed, May 22, 2002 at 09:57:24AM +0100, Doug Rabson wrote:
> On Monday 20 May 2002 3:49 am, Terry Lambert wrote:
> > Steve Kargl wrote:
> > > > Use "-ggdb" instead, thus avoiding DWARF.
> > >
> > > BZZZT... Thanks for play!
-ggdb means to use the most "expressive" debugging format the compiler
On Wednesday 22 May 2002 6:49 pm, David O'Brien wrote:
> On Wed, May 22, 2002 at 09:57:24AM +0100, Doug Rabson wrote:
> > GDB 5.2 works pretty well with -current - I've been using it recently. I
> > plan to upgrade GDB in -current to 5.2 soon (as soon as David has enough
> > time to sort out the C
On Wed, May 22, 2002 at 09:57:24AM +0100, Doug Rabson wrote:
> GDB 5.2 works pretty well with -current - I've been using it recently. I plan
> to upgrade GDB in -current to 5.2 soon (as soon as David has enough time to
> sort out the CVS magic).
I fail to see your patches to gdb 5.2 for the ker
On Monday 20 May 2002 3:49 am, Terry Lambert wrote:
> Steve Kargl wrote:
> > > Use "-ggdb" instead, thus avoiding DWARF.
> >
> > BZZZT... Thanks for play!
>
> Did Mark Peek's suggestion of using the gdb that matched
> the compiler (gdb 5.2 from ports) work instead?
GDB 5.2 works pretty well with
Steve Kargl wrote:
> > Use "-ggdb" instead, thus avoiding DWARF.
>
> BZZZT... Thanks for play!
Did Mark Peek's suggestion of using the gdb that matched
the compiler (gdb 5.2 from ports) work instead?
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
On Sun, May 19, 2002 at 05:50:32PM -0700, Terry Lambert wrote:
>
> > Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.
>
> Use "-ggdb" instead, thus avoiding DWARF.
>
BZZZT... Thanks for play!
kargl[204] gcc -ggdb a.c
kargl[205] gdb a.out
GNU gdb 4.18
Copyright 1998 Free Software Foun
Steve Kargl wrote:
> Finally, since you're quick with the wit, can you tell me
> how to debug the following problem when I can't compile
> the debugger.
[ ... ]
> gcc -g a.c
[ ... ]
> Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.
Use "-ggdb" instead, thus avoiding DWARF.
-- Terry
On 2002-05-19 17:00, Matthew Dillon wrote:
>
> :> You know, every time I update my -current sources it's winding up
> :> taking me an entire day to get things to build again.
> :
> :There are cases where updating with the `new files' requires that you
> :have updated to the `new files', a
:> You know, every time I update my -current sources it's winding up
:> taking me an entire day to get things to build again.
:
:There are cases where updating with the `new files' requires that you
:have updated to the `new files', aka chicken and egg problems. This
:is true with the -D
On 2002-05-19 13:31, Matthew Dillon wrote:
> David O'Brien wrote:
>:
>:Because we are wanting for people to let the dust settle on the switch to
>:GCC 3.1. It is best for people to juse use -DNO_WERROR for now.
>:Patience.
>
> Ahhh.. so *that's* why everything broke when I did a full update.
At 2:58 PM -0700 5/19/02, Steve Kargl wrote:
>Finally, since you're quick with the wit, can you tell me
>how to debug the following problem when I can't compile
>the debugger.
>
>kargl[223] cat a.c
>#include
>int main(void) {
>/* This isn't the problem. The problem is with gdb. */
>abort
On Sun, May 19, 2002 at 02:19:27PM -0700, Terry Lambert wrote:
> Both Twins: "Wonder Twin powers, Activate!"
>
> Jayna:"Take the form of ... patches!"
> Zan: "Take the form of ... a complaining email!"
> Gleek the code monkey:"Gleek! Gleek! Gleek!"
>
Terr
David O'Brien wrote:
> > > Warnings are treated as errors. Since GCC 3.1 has brought a hell of a
> > > lot more warnings with us, you should use -DNO_WERROR until the dust
> > > of the GCC 3.1 import settles down.
> >
> > If everyone is using -DNO_WERROR, then who would report build
> > problems
:> > lot more warnings with us, you should use -DNO_WERROR until the dust
:> > of the GCC 3.1 import settles down.
:>
:> If everyone is using -DNO_WERROR, then who would report build
:> problems :-).
:
:Because we are wanting for people to let the dust settle on the switch to
:GCC 3.1. It is be
On Sat, May 18, 2002 at 08:12:15PM -0700, Steve Kargl wrote:
> > Warnings are treated as errors. Since GCC 3.1 has brought a hell of a
> > lot more warnings with us, you should use -DNO_WERROR until the dust
> > of the GCC 3.1 import settles down.
>
> If everyone is using -DNO_WERROR, then who
On 2002-05-18 20:12, Steve Kargl wrote:
> On Sun, May 19, 2002 at 05:31:08AM +0300, Giorgos Keramidas wrote:
> > Warnings are treated as errors. Since GCC 3.1 has brought a hell
> > of a lot more warnings with us, you should use -DNO_WERROR until
> > the dust of the GCC 3.1 import settles down.
>
On Sun, May 19, 2002 at 05:31:08AM +0300, Giorgos Keramidas wrote:
> On 2002-05-18 12:56, Steve Kargl wrote:
> > ===> gnu/usr.bin/binutils/gdb
> > cc -O -pipe -march=athlon -D_GNU_SOURCE -I.
>-I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb
>-I/usr/src/gnu/usr.bin/bin
On 2002-05-18 12:56, Steve Kargl wrote:
> ===> gnu/usr.bin/binutils/gdb
> cc -O -pipe -march=athlon -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386
>-I/usr/src/gnu/usr.bin/binutils/gdb
>-I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386
>-I/usr/src/gnu/usr.bin/binutils/gdb/../../../.
===> gnu/usr.bin/binutils/gdb
cc -O -pipe -march=athlon -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386
-I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386
-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include
-Dprint_insn_i386=pr
26 matches
Mail list logo
