gmane.comp.emulators.tn5250

Guidelines for LINUX5250 mailing list

2013-05-01T11:30:19

Monthly posting of the guidelines for participation in the LINUX5250
Mailing List.

Answers to common questions, including installation issues for FreeBSD,
Linux and Windows are included in the documentation in the README file
in the source tarball, the manual included with the Windows installer,
and the other documentation found on our web site at
http://tn5250.sourceforge.net

Answers to other questions which may have already been asked are available in
the linux5250 email list archive, which is available at
http://archive.midrange.com/linux5250/

Keep to the subject. The topic of the list is the Linux Tn5250
Emulation project. (Though, the name "Linux" is a misnomer, since
the software will work in Microsoft Windows and any modern Unix or
Unix-like operating system)

When quoting messages, do not quote the entire message. Just quote the
parts that are needed to make the appropriate references.

Flames are absolutely prohibited. If you disagree with someone, feel
free to argue the facts, but no personal attacks will be tolerated.

The official language of the LINUX5250 Mailing List is English.

Do not post personal messages. Please use direct E-Mail. This list is
international in scope and personal messages just end up costing money.

Please do not use HTML to format messages ... not everyone has a HTML
enabled message reader and the extra text can (and does) cause some
mail readers to truncate messages.

While the participants of this list are happy to answer questions and
help solve problems, it is greatly appreciated if you do some of your
own research beforehand. Before posting a question for the first time,
please take a moment to review Eric Raymonds excellent FAQ "How to Ask
Questions the Smart Way" (http://www.catb.org/~esr/faqs/smart-questions.html).

Advertising products, repeated postings, etc, are strictly prohibited.
Also, if you have a solution that will specificly help another
participant, feel free to tell that person. And finally, if you are a
vendor, please identify yourself as such... do not try to pass yourself
off as a user of your own products (even if you are).

PLEASE NOTE: When posting to the list, any personally identifying
information in your message will be included in the list. Email
addresses, however, are masked when being formatted for the list
archives. If you include a standard signature in all messages, consider
using the internet standard for signature separator (as defined in RFC
3676, http://tools.ietf.org/html/rfc3676) of '-- ' (that's dash dash
space). The list archiving software will automatically stop including
the message when it encounters the marker.

PLEASE do not report list messages to your mail providers abuse / spam
department. This results in a black mark against midrange.com and,
depending on the mail provider's policies, can cause mail delivery
delays for everyone who uses both midrange.com with that mail provider.
midrange.com does treat abuse reports very seriously and acts upon them
immediately. When abuse reports are received, and the reporting person
can be identified, they will be removed from all lists immediately ...
and then a follow-up email will be sent.

If you wish to be unsubscribed from a list and cannot do so through the
normal mechanisms (identified at the bottom of every list message),
please contact the list owner or support-Zwy7GipZuJhWk0Htik3J/w< at >public.gmane.org for assistance.

By posting to this mailing list, you are granting MIDRANGE dot COM and
David Gibbs (david-Zwy7GipZuJhWk0Htik3J/w< at >public.gmane.org) non-exclusive, unlimited, rights to
republish its contents.

This list IS copyrighted as a compilation. Republication of this mailing
list, for anything other than personal use, without the explicit permission
of the list owner is a violation of U.S. Copyright Law and will be dealt
with as such.

Collecting or "Mining" of email address from this forum, or any related
web archive, is strictly and explicitly prohibited (not to mention that
it is extraordinarily unprofessional).

Violation of the above guidelines will be determined by the moderator
and will result either a) The offending party will be forced to make
major modifications to a 10 year old, matching records, RPG II program
that uses every available indicator or b) permanent disconnection from
the conference (you decide which is worse).

To subscribe, unsubscribe, or change mailing list options, please vist
http://lists.midrange.com/mailman/listinfo/LINUX5250

If you have questions or comments about these guidelines, please feel
free to contact the moderator, David Gibbs via internet e-mail at
linux5250-owner-Zwy7GipZuJgU04JRNCRQjg< at >public.gmane.org

MIDRANGE dot COM is a non-commercial organization and is not connected
with any corporation, periodical, or commercial enterprise. For more
information, send Internet E-Mail to support-Zwy7GipZuJgU04JRNCRQjg< at >public.gmane.org

Re: 0.17.4 Win32 paste bug and possible fix

Ken Koehler — 2013-04-18T19:37:51

   Wow, we've been choking on that one for years.
   As soon as I can make the time I'll try it.
   Thanks!

   ------ Original Message ------
   Received: 03:29 PM EDT, 04/18/2013
   From: Buck Calabro <kc2hiz-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>
   To: linux5250-Zwy7GipZuJhWk0Htik3J/w< at >public.gmane.org
   Subject: [LINUX5250] 0.17.4 Win32 paste bug and possible fix

     I love tn5250 and am grateful that we have a community of people who
     support it. I myself am barely able to walk through the code so I
     appreciate the list looking over my shoulder...

     I had a long standing bug whereby I would copy some long-ish SQL out of
     a Word document and paste it into my tn5250 session and the session
     would crash with a Windows message saying that tn5250.exe has stopped
     working. I could never put my finger on the exact circumstances, and it
     never bothered me that much until recently when I had to do a LOT of
     these.

     So I started digging. Got to win32_paste_text_selection and started
     putting in TN5250_LOG() statements. Too busy to learn gdb :-( I
     eventually narrowed the error down to the bottom, 'free(pNewBuf);'
     Which didn't make much sense to me unless something had inadvertently
     stepped on pNewBuf. I'm still not a C programmer despite several hours
     of looking at the code (ha!), but the only place it looks like this
     routine could possibly step on pNewBuf is up above, where it says 'just
     a precaution'.

     if (hBuf != NULL) {
     size = GlobalSize(hBuf);
     size++;
     TN5250_LOG (("Windows clipboard size %d\n", size));
     pNewBuf = malloc(size);
     pBuf = GlobalLock(hBuf);
     strncpy(pNewBuf, pBuf, size);
     pNewBuf[size] = '\0'; /* just a precaution */
     GlobalUnlock(hBuf);
     }

     I added the line to increment size and my paste problem has gone away.
     Take it out, and it returns.

     I hope this makes sense.
     --buck
     --
     This is the Linux 5250 Development Project (LINUX5250) mailing list
     To post a message email: LINUX5250-Zwy7GipZuJhWk0Htik3J/w< at >public.gmane.org
     To subscribe, unsubscribe, or change list options,
     visit: http://lists.midrange.com/mailman/listinfo/linux5250
     or email: LINUX5250-request-Zwy7GipZuJhWk0Htik3J/w< at >public.gmane.org
     Before posting, please take a moment to review the archives
     at http://archive.midrange.com/linux5250.

0.17.4 Win32 paste bug and possible fix

Buck Calabro — 2013-04-18T19:29:10

I love tn5250 and am grateful that we have a community of people who
support it.  I myself am barely able to walk through the code so I
appreciate the list looking over my shoulder...

I had a long standing bug whereby I would copy some long-ish SQL out of
a Word document and paste it into my tn5250 session and the session
would crash with a Windows message saying that tn5250.exe has stopped
working.  I could never put my finger on the exact circumstances, and it
never bothered me that much until recently when I had to do a LOT of these.

So I started digging.  Got to win32_paste_text_selection and started
putting in TN5250_LOG() statements.  Too busy to learn gdb :-(  I
eventually narrowed the error down to the bottom, 'free(pNewBuf);'
Which didn't make much sense to me unless something had inadvertently
stepped on pNewBuf.  I'm still not a C programmer despite several hours
of looking at the code (ha!), but the only place it looks like this
routine could possibly step on pNewBuf is up above, where it says 'just
a precaution'.

if (hBuf != NULL) {
    size = GlobalSize(hBuf);
    size++;
    TN5250_LOG (("Windows clipboard size %d\n", size));
    pNewBuf = malloc(size);
    pBuf = GlobalLock(hBuf);
    strncpy(pNewBuf, pBuf, size);
    pNewBuf[size] = '\0'; /* just a precaution */
    GlobalUnlock(hBuf);
}

I added the line to increment size and my paste problem has gone away.
Take it out, and it returns.

I hope this makes sense.
  --buck

Guidelines for LINUX5250 mailing list

2013-04-01T11:30:17