<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/os2linux/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/os2linux/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 29 Jun 2005 14:07:05 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/os2linux/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>Invalid Buffer in DosGetMessage</title><link>https://sourceforge.net/p/os2linux/bugs/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I found a bug in the implementation of DosGetMessage. &lt;br /&gt;
It seems the call to "catclose" should be made after&lt;br /&gt;
the strcpy call that uses "catPtr".  Right now, the&lt;br /&gt;
catalog is closed before the string copy and that&lt;br /&gt;
results in a segmentation violation because the memory&lt;br /&gt;
associated with catPtr gets free'd in the close call. &lt;br /&gt;
Also, you might consider using "strncpy" rather than&lt;br /&gt;
"strcpy" to avoid overwriting the target buffer if the&lt;br /&gt;
message is too long.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Ashley</dc:creator><pubDate>Wed, 29 Jun 2005 14:07:05 -0000</pubDate><guid>https://sourceforge.net249905227d79d616c5e82dbc1a68981b692d9d7e</guid></item></channel></rss>