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: (Another) Segfault in varobj.c

From: "Robert Norton" <rnorton at broadcom dot com>
To: "Vladimir Prus" <ghost at cs dot msu dot su>, gdb at sources dot redhat dot com
Date: Tue, 7 Aug 2007 09:10:57 -0700
Subject: RE: (Another) Segfault in varobj.c
References: <B0D822BFECD50F4991F2516EA50F273C021ABDD7@NT-IRVA-0752.brcm.ad.broadcom.com> <f9a1ti$kv1$1@sea.gmane.org>

> -----Original Message-----
> From: gdb-owner@sourceware.org 
> [mailto:gdb-owner@sourceware.org] On Behalf Of Vladimir Prus
> Sent: 07 August 2007 16:09
> To: gdb@sources.redhat.com
> Subject: Re: (Another) Segfault in varobj.c
>
> It's hard to say without knowing if you have any local 
> changes in varobj.c

Only an attempt to fix another bug which apparently is fixed in CVS
anyway.

> If not, then just grabbing varobj.c and maybe mi/* should be safe --
> at least as far as my patches are concerned, they are local 
> to varobj.c.

OK. This is mostly what I wanted to know. I'll give it a try!

Robert

Follow-Ups:
- RE: (Another) Segfault in varobj.c
  - From: Robert Norton

References:
- (Another) Segfault in varobj.c
  - From: Robert Norton
- Re: (Another) Segfault in varobj.c
  - From: Vladimir Prus

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