Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Robert Norton <rnorton@broadcom.com>
Cc: Michael Snyder <msnyder@vmware.com>,
	"gdb@sourceware.org" 	<gdb@sourceware.org>,
	Ralf Corsepius <ralf.corsepius@rtems.org>
Subject: Re: core dump when watchpoint set
Date: Fri, 12 Sep 2008 16:11:00 -0000	[thread overview]
Message-ID: <48CA948F.1080705@oarcorp.com> (raw)
In-Reply-To: <2DFD360E328B3941911E6D28B085D990100831A99F@SJEXCHCCR01.corp.ad.broadcom.com>

Robert Norton wrote:
>> -----Original Message-----
>> From: gdb-owner@sourceware.org
>> [mailto:gdb-owner@sourceware.org] On Behalf Of Michael Snyder
>> Sent: 09 September 2008 23:10
>> To: Joel Sherrill
>> Cc: gdb@sourceware.org
>> Subject: Re: core dump when watchpoint set
>>
>> Hmmm, yeah, a null value is being passed up, resulting in
>> a null type being sent to value_type, which dereferences it
>> without null-checking.
>>
>> And in fact, the current source (breakpoint.c) does check
>> b->val != NULL before it makes the corresponding call.
>>
>> So you can expect that this is fixed.
>>     
>
> In fact I fixed exactly this bug in our 6.8 port this week by applying this patch:
>
> http://sourceware.org/ml/gdb-patches/2008-02/msg00472.html
>
>   
Thank you.  I can confirm it fixes the issue when used with psim
as well.

Ralf.. could you add this patch to the RTEMS gdb 6.8 set?  Thanks.
> Robert
>
>   


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985



      reply	other threads:[~2008-09-12 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 14:57 Joel Sherrill
2008-09-09 22:11 ` Michael Snyder
2008-09-12 15:25   ` Robert Norton
2008-09-12 16:11     ` Joel Sherrill [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48CA948F.1080705@oarcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=ralf.corsepius@rtems.org \
    --cc=rnorton@broadcom.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox