when i run valgrind-3.13.0 getting this below unhandled instruction: 0xDEFF 0x1A9B
--5896-- REDIR: 0x4cdee24 (libc.so.6:calloc) redirected to 0x4837bc8 (calloc)
--5896-- REDIR: 0x4ce30e4 (libc.so.6:strncmp) redirected to 0x4839afc (strncmp)
--5896-- REDIR: 0x4ce698c (libc.so.6:strchrnul) redirected to 0x483d88c (strchrnul)
--5896-- REDIR: 0x4ce3224 (libc.so.6:strncpy) redirected to 0x48395bc (strncpy)
--5896-- REDIR: 0x4cde9c4 (libc.so.6:free) redirected to 0x4836ac0 (free)
--5896-- REDIR: 0x4ce2f9c (libc.so.6:strnlen) redirected to 0x483910c (strnlen)
--5896-- REDIR: 0x4ce2411 (libc.so.6:strcmp) redirected to 0x483a414 (strcmp)
--5896-- REDIR: 0x4ce4b60 (libc.so.6:strcasecmp) redirected to 0x4839dec (strcasecmp)
--5896-- REDIR: 0x4ce333c (libc.so.6:strpbrk) redirected to 0x483e3b0 (strpbrk)
--5896-- REDIR: 0x4ce42dc (libc.so.6:bcmp) redirected to 0x483c53c (bcmp)
--5896-- REDIR: 0x4bc3841 (libstdc++.so.6:operator new(unsigned int)) redirected to 0x4835c68 (operator new(unsigned int))
--5896-- REDIR: 0x4bc1f19 (libstdc++.so.6:operator delete(void*)) redirected to 0x4837120 (operator delete(void*))
--5896-- REDIR: 0x4ce3ce4 (libc.so.6:strstr) redirected to 0x483e200 (strstr)
--5896-- REDIR: 0x4bc38c5 (libstdc++.so.6:operator new[](unsigned int)) redirected to 0x4836518 (operator new[](unsigned int))
--5896-- REDIR: 0x4cdead0 (libc.so.6:realloc) redirected to 0x4837e34 (realloc)
--5896-- REDIR: 0x4bc1f25 (libstdc++.so.6:operator delete[](void*)) redirected to 0x4837780 (operator delete[](void*))
--5896-- REDIR: 0x4ce4bb8 (libc.so.6:strncasecmp) redirected to 0x4839ea4 (strncasecmp)
--5896-- REDIR: 0x4ce2710 (libc.so.6:stpcpy) redirected to 0x483c6b4 (stpcpy)
disInstr(thumb): unhandled instruction: 0xDEFF 0x1A9B
--5896-- Caught __NR_exit; running __gnu_cxx::__freeres and __libc_freeres() wrapper
==5896==
==5896== HEAP SUMMARY:
==5896== in use at exit: 60,454 bytes in 3,246 blocks
==5896== total heap usage: 3,667 allocs, 421 frees, 281,586 bytes allocated
Why does it occur ? does it need to patch valgrind?
Related
I have two domains: example.com and example.org.
HTTP://www.example.com redirects to HTTPS://www.example.org (as expected)
HTTP://example.com redirects to HTTPS://www.example.org (as expected)
HTTP://www.example.org redirects to HTTPS://www.example.org (as expected)
HTTP://example.org redirects to HTTPS://www.example.org (as expected)
HTTPS://example.org redirects to HTTPS://www.example.org (as expected)
However, using HTTPS doesn't work. I think this is because I haven't proven that I own example.com to my CA (letsencrypt through GitHub pages).
HTTPS://www.example.com should redirect to HTTPS://www.example.org
HTTPS://example.com should redirect to HTTPS://www.example.org
This question is related but it goes a little over my head and I'm not sure how to implement it on Github pages with Namecheap.
I solved this by migrating to netlify. I recommend.
I used the information here and here to create a _redirects file that looks like this:
https://example.com/* https://www.example.org/:splat 301!
https://www.example.com/* https://www.example.org/:splat 301!
http://example.com/* https://www.example.org/:splat 301!
http://www.example.com/* https://www.example.org/:splat 301!
I have a S3 static website set up using CloudFront for HTTPS. I'm trying to add redirect rules, but I can't get it all to work together.
I have a Cloudfront distribution for www.mysite.com pointing at mysite.s3-website.us-east-2.amazonaws.com. This works great. It serves the default index page and custom error page. However, I now want to move page1 to page2. I tried setting up a redirect rule:
<RoutingRule>
<Condition>
<KeyPrefixEquals>page1</KeyPrefixEquals>
</Condition>
<Redirect>
<ReplaceKeyWith>page2</ReplaceKeyWith>
</Redirect>
</RoutingRule>
The redirect is triggered; however, it redirects away from mysite.com/page1 -> mysite.s3-website.us-east-2.amazonaws.com/page2!
Note: I can't use 301 redirect pages because some of the actual redirects are hash-related.
Any suggestions?
I remember we had the following,
<RoutingRule>
<Condition>
<KeyPrefixEquals>page1</KeyPrefixEquals>
</Condition>
<Redirect>
<HostName>www.mysite.com</HostName>
<ReplaceKeyWith>page2</ReplaceKeyWith>
</Redirect>
</RoutingRule>
Hope it helps.
Case:
I have a website www.xyz.com/ with folder / abc
I have made a subdomain abc.xyz.com which points (on the webserver) to the /abc folder
I would like to make it impossible for people to access www.xyz.com/abc and be redirected to abc.xyz.com
tried
a normal 301 redirect results in people also being redirected when they go to abc.xyz.com (so error for too many redirects).
Thank you.
I got it after a few trials and errors:
Redirect 301 /abc/ https://abc.xyz.com
I have a website with a structure similar to the following:
/
-- /public/
-- index.php
-- login.php
-- contact.php
Normally on the user is not logged in then he gets redirected to login.php.
So basically when the user types myWebSite.com/ he gets redirected to the index page which redirects him to the login page.
I have added a temp landing page that I want the user redirected to in he does not specify a page in the URL.
Examples:
myWebSite.com/index.php --> index.php
myWebSite.com/login.php --> login.php
However if he does not specify the page then he will be redirected to the new landing page, like so:
myWebSite.com/ --> new landing page
myWebSite.com --> new landing page
With the landing page added the structure is similar to the following:
/
-- /public/
-- index.php
-- login.php
-- contact.php
-- /landing/
-- index.php // new landing page
I known that this can be done using the PHP in the index file. However it will be cleaner to do it in an .htaccss file and also the PHP file can be overwritten by automatic update.
I have tried to several times and failed:
Redirect 301 / /landing/index.php
----------------------------------------------
RedirectMatch 301 /(.*) /landing/index.php$1
Also is there a way to hide landing directory from the URL? even if that means renaming /landing/index.php to landing.php to avoid conflict between it and /index.php
Notes:
I have enabled and tested mod rewrite.
If I have a file named /a.php, and with .htaccess I redirected that URL to /b.php with 301 flag. For the SEO sake, I have to use 301 flag. But what if I need to get back to /a.php ??? Browser which once faced that 301 redirect will remember this and do redirect until the remove cookies themselves. So What should be my plan???
But what if I need to get back to /a.php ???
Then you remove the 301 redirect to the b.php file and create a new 301 redirect to the a.php file when the b.php file is requested. Even if browsers remember that a->b, when the browser requests b.php, it'll be 301 redirected back to a. As long as the old 301 redirect isn't there, the browser will then try to load a.php.