This is the mail archive of the gdb-patches@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: [patch] avoid the crash of gdb+pretty printer on initialized local variables

From: Tom Tromey <tromey at redhat dot com>
To: asmwarrior <asmwarrior at gmail dot com>
Cc: gdb-patches at sourceware dot org
Date: Mon, 05 Dec 2011 14:44:26 -0700
Subject: Re: [patch] avoid the crash of gdb+pretty printer on initialized local variables
References: <4ED379D8.4060808@gmail.com> <4ED8534D.2050100@gmail.com> <m3wrae9au9.fsf@fleche.redhat.com> <4EDAD0B3.80505@gmail.com>

>>>>> ">" == ext asmwarrior <asmwarrior@gmail.com> writes:

Tom> I forget, something to do with not using the right gcc flag?

>> My app was build with -O0 and -g, no extra flag is used.

I mean a missing flag when building gdb.  I vaguely recall a need for
-fno-omit-frame-pointer, and that without this, gdb exceptions cause
crashes.

Tom

Follow-Ups:
- Re: [patch] avoid the crash of gdb+pretty printer on initialized local variables
  - From: asmwarrior

References:
- [patch] avoid the crash of gdb+pretty printer on initialized local variables
  - From: asmwarrior
- Re: [patch] avoid the crash of gdb+pretty printer on initialized local variables
  - From: Tom Tromey
- Re: [patch] avoid the crash of gdb+pretty printer on initialized local variables
  - From: asmwarrior

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