From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] realloc null pointer
Date: Sun, 04 Jan 2015 11:30:25 -0500 [thread overview]
Message-ID: <20150004113025.eklhad@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
This horrible long url
https://maps.google.com/maps?hl=en&gbv=1&ie=UTF-8&fb=1&gl=us&ftid=0x8824960112ae4ca1:0xe09071020c10f93d&q=2660+Dixie+Hwy,+Waterford+Township,+MI+48328&ei=vGGpVOrBBoqsyQSt0oGoAw&ved=0CBQQ8gEoADAA&output=classic&dg=brw
Produces a realloc null pointer fatal error on my system.
I ran it with db5, even db7, but still not clrear what is going on.
I check for this null pointer and exit gracefully, but maybe I shouldn't.
Maybe I should check and print the error, then deliberately set *s = 55,
to get the null pointer dereference and the stack trace.
Karl Dahlke
next reply other threads:[~2015-01-04 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 16:30 Karl Dahlke [this message]
2015-01-05 16:24 ` Adam Thompson
2015-01-05 16:41 Karl Dahlke
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=20150004113025.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.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;
as well as URLs for NNTP newsgroup(s).