From: Daniel Jacobowitz <drow@false.org>
To: Denis PILAT <denis.pilat@st.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFA] gdbserver with reversed arguments seg. fault
Date: Wed, 03 Jan 2007 14:44:00 -0000 [thread overview]
Message-ID: <20070103144423.GB12452@nevyn.them.org> (raw)
In-Reply-To: <459B778D.4000500@st.com>
On Wed, Jan 03, 2007 at 10:29:49AM +0100, Denis PILAT wrote:
> Hi,
>
> Following our discussion in the thread
> http://sources.redhat.com/ml/gdb-patches/2007-01/msg00059.html
> I'm proposing the attached patch to fix a segmentation fault that occurs
> into gdbserver when you revert the binary filename with the "host:port"
> argument.
> In inferiors.c the inferior_target_data() function is called with a NULL
> pointer argument. At the beginning I though of testing arguments but
> none of them are tested in this whole file so I concluded it's up to the
> caller to do so.
What exactly did you do to get this crash? What's the backtrace look
like? It didn't happen for me.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-03 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 9:30 Denis PILAT
2007-01-03 14:44 ` Daniel Jacobowitz [this message]
2007-01-03 15:02 ` Denis PILAT
2007-01-03 17:58 ` Daniel Jacobowitz
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=20070103144423.GB12452@nevyn.them.org \
--to=drow@false.org \
--cc=denis.pilat@st.com \
--cc=gdb-patches@sourceware.org \
/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