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: Tue, 06 Dec 2011 08:40:24 -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> <m31usipubp.fsf@fleche.redhat.com> <4EDDAD62.9000103@gmail.com>

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

>> I forget to mention that My gdb was build with -O0 and -g, so I think
>> no optimization was used in building gdb.

>> The problem is that gdb still crash when it try to pretty-print the
>> uninitialized local variables.

I think the best thing to do is find out why that happens, and fix the
root cause.  gdb should not crash.

Tom

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
- 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]