Is the Mantis bug reporter still working? I notice that no bugs have
been confirmed/acknowledged since the start of the year, and the only
notifications I've received from the site have been when somebody posts
a spam link as a comment....
--
Harriet Bazley == Loyaulte me lie ==
It is impossible to enjoy idling thoroughly unless one has plenty of work to do
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Monday, 11 April 2022
Saturday, 9 April 2022
Re: Facebook notifications
On 9 Apr 2022 as I do recall,
Harriet Bazley wrote:
> I've been using Netsurf with m.facebook.com - as of this morning, the
> 'notification' links that are displayed when, for example, someone
> responds to a Facebook comment are not working when you click on them.
> ("Sorry, something went wrong. We are working on it and we'll get it
> fixed as soon as we can.")
>
> Have Facebook changed something in the link syntax?
>
Going back through the activity history, it looks as if the issue is not
the notification links per se, but displaying *any* FB page that I have
previously commented on, navigated to by any means - presumably Facebook
have done something fancy to add a new feature of some sort to pages
with 'user's own comments', and in some manner it has broken Netsurf's
ability to communicate with the site when loading such pages. :-(
--
Harriet Bazley == Loyaulte me lie ==
The fact that you're paranoid.... doesn't mean they're NOT out to get you.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Harriet Bazley wrote:
> I've been using Netsurf with m.facebook.com - as of this morning, the
> 'notification' links that are displayed when, for example, someone
> responds to a Facebook comment are not working when you click on them.
> ("Sorry, something went wrong. We are working on it and we'll get it
> fixed as soon as we can.")
>
> Have Facebook changed something in the link syntax?
>
Going back through the activity history, it looks as if the issue is not
the notification links per se, but displaying *any* FB page that I have
previously commented on, navigated to by any means - presumably Facebook
have done something fancy to add a new feature of some sort to pages
with 'user's own comments', and in some manner it has broken Netsurf's
ability to communicate with the site when loading such pages. :-(
--
Harriet Bazley == Loyaulte me lie ==
The fact that you're paranoid.... doesn't mean they're NOT out to get you.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Facebook notifications
I've been using Netsurf with m.facebook.com - as of this morning, the
'notification' links that are displayed when, for example, someone
responds to a Facebook comment are not working when you click on them.
("Sorry, something went wrong. We are working on it and we'll get it
fixed as soon as we can.")
Have Facebook changed something in the link syntax?
--
Harriet Bazley == Loyaulte me lie ==
Flee at once, all is discovered.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
'notification' links that are displayed when, for example, someone
responds to a Facebook comment are not working when you click on them.
("Sorry, something went wrong. We are working on it and we'll get it
fixed as soon as we can.")
Have Facebook changed something in the link syntax?
--
Harriet Bazley == Loyaulte me lie ==
Flee at once, all is discovered.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org
Monday, 4 April 2022
Re: [gccsdk] OpenSSL issues
I rebuild the library and it worked .. not sure where was going on.
Ssl now imports and works, and pip downloads a file .. although I now need need to get it to unpack the wheel ..
Small steps .. :)
Sent from my iPhone
On 4 Apr 2022, at 13:34, Chris Johns <chris@lessthan3.org.uk> wrote:
yone any ideas?If *showregs gives a valid value for r15, and that is within a library,thenFrustratingly it doesn't (is claims all rhe registers are zero)... might just have to go down the "shove in some printf's" route.
Cheers
Chris_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Re: [gccsdk] OpenSSL issues
Re: [gccsdk] OpenSSL issues
On 04/04/2022 10:10, Chris Johns wrote:
> Hi
>
> I'm trying to track down an issue with ssl in python, which used OpenSSL
> 1.1. To try to reduce the number of moving parts, I've managed to narrow
> it down to a smaller test.
>
> The setup is .. the C code below (which runs fine on linux) has been
> compiled on RISC OS (native) with GCC10 (buult from the auto builder).
> LibSSL (1.1.0) is the one I built with the auto-builder, but I had to
> tweak it to use the 1.1.0n (rather than m) sources and I built it for
> armv6z (IIRC) instaad of armv3.
[snip]
> Anyone any ideas?
If *showregs gives a valid value for r15, and that is within a library,
then
*somaddress pc
should tell you which library and where. You can then use the library
offset given together with the output from
*nm -Dn <library>
to determine which function the crash occurs in. Finally, a few
printf's in the offending function to narrow it down even further.
That's what I usually do.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
> Hi
>
> I'm trying to track down an issue with ssl in python, which used OpenSSL
> 1.1. To try to reduce the number of moving parts, I've managed to narrow
> it down to a smaller test.
>
> The setup is .. the C code below (which runs fine on linux) has been
> compiled on RISC OS (native) with GCC10 (buult from the auto builder).
> LibSSL (1.1.0) is the one I built with the auto-builder, but I had to
> tweak it to use the 1.1.0n (rather than m) sources and I built it for
> armv6z (IIRC) instaad of armv3.
[snip]
> Anyone any ideas?
If *showregs gives a valid value for r15, and that is within a library,
then
*somaddress pc
should tell you which library and where. You can then use the library
offset given together with the output from
*nm -Dn <library>
to determine which function the crash occurs in. Finally, a few
printf's in the offending function to narrow it down even further.
That's what I usually do.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
[gccsdk] OpenSSL issues
Hi
I'm trying to track down an issue with ssl in python, which used OpenSSL
1.1. To try to reduce the number of moving parts, I've managed to narrow
it down to a smaller test.
The setup is .. the C code below (which runs fine on linux) has been
compiled on RISC OS (native) with GCC10 (buult from the auto builder).
LibSSL (1.1.0) is the one I built with the auto-builder, but I had to
tweak it to use the 1.1.0n (rather than m) sources and I built it for
armv6z (IIRC) instaad of armv3.
#include <openssl/ssl.h>
int main(void)
{
SSL_CTX *ctx = SSL_CTX_new( TLS_client_method() );
printf("ctx: %x\n", ctx);
printf("load_verify_locations: %d\n",
SSL_CTX_load_verify_locations(ctx, "cacert.pem", NULL) );
SSL_CTX_free(ctx);
printf("Bye!\n");
}
*gcc -c ssltest.c -ILibSSL11:
*gcc ssltest.o -o ssltest -LLibSSLl11: -lssl -lcrypto -ldl
*ssltest
ctx: 71a88
Fatal signal received: Segmentation fault
Stack backtrace:
Running thread 0x58834 (Main Thread)
(50df5f40) lr: 48fa9dbc : 7ADBC :
SharedLibs:lib.armeabihf.libunixlib/so/5/0/0
(50df5fb0) lr: 48fab450 : 7C450 :
SharedLibs:lib.armeabihf.libunixlib/so/5/0/0
(50df5fb4) lr: 50ef6d3c
(48fab450) lr: ef020014
Stack frame has gone out of bounds with address ebfff8ec
*
If I rename the pem file, it reports SSL_CTX_load_verify_locations: 0
(which one would expect) then has a similar error (wihtout pritning Bye!)
Anyone any ideas?
Cheers
Chris
--
Chris Johns
This email is measured by weight not volume - contents may settle during
transit.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
I'm trying to track down an issue with ssl in python, which used OpenSSL
1.1. To try to reduce the number of moving parts, I've managed to narrow
it down to a smaller test.
The setup is .. the C code below (which runs fine on linux) has been
compiled on RISC OS (native) with GCC10 (buult from the auto builder).
LibSSL (1.1.0) is the one I built with the auto-builder, but I had to
tweak it to use the 1.1.0n (rather than m) sources and I built it for
armv6z (IIRC) instaad of armv3.
#include <openssl/ssl.h>
int main(void)
{
SSL_CTX *ctx = SSL_CTX_new( TLS_client_method() );
printf("ctx: %x\n", ctx);
printf("load_verify_locations: %d\n",
SSL_CTX_load_verify_locations(ctx, "cacert.pem", NULL) );
SSL_CTX_free(ctx);
printf("Bye!\n");
}
*gcc -c ssltest.c -ILibSSL11:
*gcc ssltest.o -o ssltest -LLibSSLl11: -lssl -lcrypto -ldl
*ssltest
ctx: 71a88
Fatal signal received: Segmentation fault
Stack backtrace:
Running thread 0x58834 (Main Thread)
(50df5f40) lr: 48fa9dbc : 7ADBC :
SharedLibs:lib.armeabihf.libunixlib/so/5/0/0
(50df5fb0) lr: 48fab450 : 7C450 :
SharedLibs:lib.armeabihf.libunixlib/so/5/0/0
(50df5fb4) lr: 50ef6d3c
(48fab450) lr: ef020014
Stack frame has gone out of bounds with address ebfff8ec
*
If I rename the pem file, it reports SSL_CTX_load_verify_locations: 0
(which one would expect) then has a similar error (wihtout pritning Bye!)
Anyone any ideas?
Cheers
Chris
--
Chris Johns
This email is measured by weight not volume - contents may settle during
transit.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
Subscribe to:
Posts (Atom)