public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "chris_douglas_email at yahoo dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31152] Formalise unintened functionality in version 9.1 Date: Sat, 30 Dec 2023 20:12:42 +0000 [thread overview] Message-ID: <bug-31152-4717-nnxrSdbYZ5@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31152-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31152 --- Comment #5 from stephen douglas <chris_douglas_email at yahoo dot com> --- As I stated in my initial post, my hobby is repurposing old tech. I look at the box as a set of peripherals with a processor in the middle costing a lot less than the cards for a PC (usually less than 10%). I write to the manufacturer, and if they consider the box obsolete, they usually tell you what they have done to prevent “piracy” if you sign an NDA. I then offer to either remove the comments from anything developed using information in the NDA and then change meaningful names to gobbledygook (a secure password generator is usually good) OR publish the .S of the .c. If we are both happy with this I sign the NDA. I then use gdb to sort out anything I miss. I cleared “encrypted” to describe what they do to file descriptors but the details are subject to the NDA. I have an unexplained change in my glibc source to increase the size of the constant(s) FD_SETSIZE is generated from so it copes. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-30 20:12 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-12 18:16 [Bug gdb/31152] New: " chris_douglas_email at yahoo dot com 2023-12-12 20:31 ` [Bug gdb/31152] " tromey at sourceware dot org 2023-12-12 20:31 ` tromey at sourceware dot org 2023-12-27 19:22 ` chris_douglas_email at yahoo dot com 2023-12-28 16:44 ` tromey at sourceware dot org 2023-12-30 20:12 ` chris_douglas_email at yahoo dot com [this message] 2023-12-30 22:34 ` tromey at sourceware dot org 2023-12-31 20:32 ` chris_douglas_email at yahoo dot com 2024-01-14 16:45 ` chris_douglas_email at yahoo dot com
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=bug-31152-4717-nnxrSdbYZ5@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).