From noreply at rubyforge.org Thu Aug 3 07:35:08 2006 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 3 Aug 2006 07:35:08 -0400 (EDT) Subject: [Win32utils-devel] [ win32utils-Bugs-5285 ] event_type is not recognized properly Message-ID: <20060803113508.F21EAA97005F@rubyforge.org> Bugs item #5285, was opened at 2006-08-03 07:35 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5285&group_id=85 Category: win32-eventlog Group: Code Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: event_type is not recognized properly Initial Comment: Ver:0.4.1 Line 469 event_type = get_event_type(buf[24,2].unpack('S').first) Should be placed into "while dwread > 0" loop. by TheR ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5285&group_id=85 From noreply at rubyforge.org Thu Aug 3 11:34:46 2006 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 3 Aug 2006 11:34:46 -0400 (EDT) Subject: [Win32utils-devel] [ win32utils-Bugs-5287 ] v 0.4.1 - Clipboard.set_data causes Segmentation fault Message-ID: <20060803153446.336AE5240DAE@rubyforge.org> Bugs item #5287, was opened at 2006-08-03 11:34 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5287&group_id=85 Category: win32-clipboard Group: Code Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: v 0.4.1 - Clipboard.set_data causes Segmentation fault Initial Comment: Whenever Clipboard.set_data is called a Segmentation fault occurs and ruby reports abnormal program shutdown. You can discover this simply by running the test case. I have observed this on two diffent systems. Version 0.4.0 still works fine. win32-clipboard-0.4.1 ruby 1.8.4 WinXP sp2 Edwin King ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5287&group_id=85 From noreply at rubyforge.org Fri Aug 4 20:28:06 2006 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Fri, 4 Aug 2006 20:28:06 -0400 (EDT) Subject: [Win32utils-devel] [ win32utils-Bugs-5287 ] v 0.4.1 - Clipboard.set_data causes Segmentation fault Message-ID: <20060805002806.B470752413C9@rubyforge.org> Bugs item #5287, was opened at 2006-08-03 08:34 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5287&group_id=85 Category: win32-clipboard Group: Code Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: v 0.4.1 - Clipboard.set_data causes Segmentation fault Initial Comment: Whenever Clipboard.set_data is called a Segmentation fault occurs and ruby reports abnormal program shutdown. You can discover this simply by running the test case. I have observed this on two diffent systems. Version 0.4.0 still works fine. win32-clipboard-0.4.1 ruby 1.8.4 WinXP sp2 Edwin King ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2006-08-04 17:28 Message: Are you sure? >ruby test\tc_clipboard.rb Loaded suite test/tc_clipboard Started ............. Finished in 0.016 seconds. 13 tests, 36 assertions, 0 failures, 0 errors What version of windows-pr are you using? - Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5287&group_id=85 From noreply at rubyforge.org Sat Aug 5 00:44:08 2006 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Sat, 5 Aug 2006 00:44:08 -0400 (EDT) Subject: [Win32utils-devel] [ win32utils-Bugs-5285 ] event_type is not recognized properly Message-ID: <20060805044408.43E185240956@rubyforge.org> Bugs item #5285, was opened at 2006-08-03 04:35 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5285&group_id=85 Category: win32-eventlog Group: Code >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Nobody (None) >Assigned to: Daniel Berger (djberg96) Summary: event_type is not recognized properly Initial Comment: Ver:0.4.1 Line 469 event_type = get_event_type(buf[24,2].unpack('S').first) Should be placed into "while dwread > 0" loop. by TheR ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2006-08-04 21:44 Message: Good catch - no idea why I did that. Anyway, it's fixed in CVS and will be part of the next release. Thanks, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5285&group_id=85 From djberg96 at gmail.com Mon Aug 7 21:39:04 2006 From: djberg96 at gmail.com (Daniel Berger) Date: Mon, 07 Aug 2006 19:39:04 -0600 Subject: [Win32utils-devel] win32 eventlog dup In-Reply-To: <20060808011620.DE94FC0B8@mx2.delmonte-phil.com> References: <20060808011620.DE94FC0B8@mx2.delmonte-phil.com> Message-ID: <44D7EB38.2040603@gmail.com> That's weird. Line 296 is just a call to FormatMessage(). Folks on the mailing list - could this be a wide character issue? Buffer too small maybe? Regards, Dan Pe?a wrote: > forgot: > > it segfaults on the win2k3 server (domain controller). > > it has _not_ segfault on my winxp pro though. > > > > # -----Original Message----- > # From: Pe?a, Botp > # Sent: Tuesday, August 08, 2006 8:52 AM > # To: 'Daniel Berger' > # Subject: RE: win32 eventlog dup > # > # Hi Daniel, > # > # I'm afraid it's not stable enough yet. > # Running it on our server, it segs (but not immediately). > # Catch is, it is not eventlog but windows-pr... > # > # c:/ruby/lib/ruby/gems/1.8/gems/windows-pr-0.5.2-mswin32/lib/wi > ndows/error.rb:296 > # : [BUG] Segmentation fault > # ruby 1.8.4 (2006-04-14) [i386-mswin32] > # > # > # thanks and kind regards -botp > # > # > # > # # -----Original Message----- > # # From: Pe?a, Botp > # # Sent: Monday, August 07, 2006 11:53 AM > # # To: 'Daniel Berger' > # # Subject: RE: win32 eventlog dup > # # > # # From: Daniel Berger [mailto:djberg96 at gmail.com] > # # # I actually already confirmed that it worked from my own > # testing and > # # # Heesob also confirmed it. It was released as part of 0.4.2, so > # # # hopefully that will work for you. :) > # # > # # Hi Daniel, > # # I just downloaded the 0.4.2 and Yes it does work! I will try > # # testing it on our servers and test it's stability. > # # > # # thank you again for everything. > # # > # # kind regards -botp > # # > > From phasis at gmail.com Mon Aug 7 22:00:11 2006 From: phasis at gmail.com (Heesob Park) Date: Tue, 8 Aug 2006 11:00:11 +0900 Subject: [Win32utils-devel] win32 eventlog dup In-Reply-To: <44D7EB38.2040603@gmail.com> References: <20060808011620.DE94FC0B8@mx2.delmonte-phil.com> <44D7EB38.2040603@gmail.com> Message-ID: Hi, The segfault happens only on tail ? Or segfaults on read too? The error causing event log backup file might be helpful for debugging. Regards, Park Heesob 2006/8/8, Daniel Berger : > That's weird. Line 296 is just a call to FormatMessage(). > > Folks on the mailing list - could this be a wide character issue? Buffer > too small maybe? > > Regards, > > Dan > > Pe?a wrote: > > forgot: > > > > it segfaults on the win2k3 server (domain controller). > > > > it has _not_ segfault on my winxp pro though. > > > > From djberg96 at gmail.com Tue Aug 8 23:36:48 2006 From: djberg96 at gmail.com (Daniel Berger) Date: Tue, 08 Aug 2006 21:36:48 -0600 Subject: [Win32utils-devel] win32 eventlog dup In-Reply-To: <20060808024919.ADFBBC0D6@mx2.delmonte-phil.com> References: <20060808024919.ADFBBC0D6@mx2.delmonte-phil.com> Message-ID: <44D95850.1030309@gmail.com> Pe?a wrote: > I hope I can help why it segs.seg implies a bug, right? > is FormatMessage always being accessed? when is it accessed? is it pure ruby? Can i place a stacktrace before the actual code? > It's pure Ruby. Well, it's using Win32API behind the scenes. FormatMessage() is being called when get_last_error is called. So, there's an error happening somewhere, but it doesn't seem to like the parameters much. I can't tell for certain without a stack trace. One thing you could do is modify the FormatMessage method (not the constant) in error.rb and print out the parameters before the call to see what they are. Thanks, Dan > > # -----Original Message----- > # From: Daniel Berger [mailto:djberg96 at gmail.com] > # Sent: Tuesday, August 08, 2006 9:39 AM > # To: Pe?a, Botp > # Cc: Development and ideas for win32utils projects > # Subject: Re: win32 eventlog dup > # > # That's weird. Line 296 is just a call to FormatMessage(). > # > # Folks on the mailing list - could this be a wide character > # issue? Buffer > # too small maybe? > # > # Regards, > # > # Dan > # > # Pe?a wrote: > # > forgot: > # > > # > it segfaults on the win2k3 server (domain controller). > # > > # > it has _not_ segfault on my winxp pro though. > # > > # > > # > > # > # -----Original Message----- > # > # From: Pe?a, Botp > # > # Sent: Tuesday, August 08, 2006 8:52 AM > # > # To: 'Daniel Berger' > # > # Subject: RE: win32 eventlog dup > # > # > # > # Hi Daniel, > # > # > # > # I'm afraid it's not stable enough yet. > # > # Running it on our server, it segs (but not immediately). > # > # Catch is, it is not eventlog but windows-pr... > # > # > # > # c:/ruby/lib/ruby/gems/1.8/gems/windows-pr-0.5.2-mswin32/lib/wi > # > ndows/error.rb:296 > # > # : [BUG] Segmentation fault > # > # ruby 1.8.4 (2006-04-14) [i386-mswin32] > # > # > # > # > # > # thanks and kind regards -botp > # > # > # > # > # > # > # > # # -----Original Message----- > # > # # From: Pe?a, Botp > # > # # Sent: Monday, August 07, 2006 11:53 AM > # > # # To: 'Daniel Berger' > # > # # Subject: RE: win32 eventlog dup > # > # # > # > # # From: Daniel Berger [mailto:djberg96 at gmail.com] > # > # # # I actually already confirmed that it worked from my own > # > # testing and > # > # # # Heesob also confirmed it. It was released as part of > # 0.4.2, so > # > # # # hopefully that will work for you. :) > # > # # > # > # # Hi Daniel, > # > # # I just downloaded the 0.4.2 and Yes it does work! I will try > # > # # testing it on our servers and test it's stability. > # > # # > # > # # thank you again for everything. > # > # # > # > # # kind regards -botp > # > # # > # > > # > > # > # > > From noreply at rubyforge.org Mon Aug 21 07:43:34 2006 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 21 Aug 2006 07:43:34 -0400 (EDT) Subject: [Win32utils-devel] [ win32utils-Bugs-5479 ] Incorrect SetLastError declarations Message-ID: <20060821114335.4E31F52414F5@rubyforge.org> Bugs item #5479, was opened at 2006-08-21 07:43 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5479&group_id=85 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: Incorrect SetLastError declarations Initial Comment: windows-pr-0.5.3 lib\windows\error.rb SetLastError = Win32API.new('kernel32', 'GetLastError', 'L', 'V') SetLastErrorEx = Win32API.new('kernel32', 'GetLastError', 'LL', 'V') Should import SetLastError instead of GetLastError. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5479&group_id=85 From Daniel.Berger at qwest.com Mon Aug 21 10:27:20 2006 From: Daniel.Berger at qwest.com (Berger, Daniel) Date: Mon, 21 Aug 2006 09:27:20 -0500 Subject: [Win32utils-devel] [ win32utils-Bugs-5479 ] Incorrect SetLastErrordeclarations Message-ID: <39AA6550E5AA554AB1456707D6E5563D0259E7A9@QTOMAE2K3M01.AD.QINTRA.COM> Fixed in CVS. > -----Original Message----- > From: win32utils-devel-bounces at rubyforge.org > [mailto:win32utils-devel-bounces at rubyforge.org] On Behalf Of > noreply at rubyforge.org > Sent: Monday, August 21, 2006 5:44 AM > To: noreply at rubyforge.org > Subject: [Win32utils-devel] [ win32utils-Bugs-5479 ] > Incorrect SetLastErrordeclarations > > > Bugs item #5479, was opened at 2006-08-21 07:43 > You can respond by visiting: > http://rubyforge.org/tracker/?func=detail&atid=411&aid=5479&gr oup_id=85 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: Incorrect SetLastError declarations Initial Comment: windows-pr-0.5.3 lib\windows\error.rb SetLastError = Win32API.new('kernel32', 'GetLastError', 'L', 'V') SetLastErrorEx = Win32API.new('kernel32', 'GetLastError', 'LL', 'V') Should import SetLastError instead of GetLastError. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5479&group_id=85 _______________________________________________ win32utils-devel mailing list win32utils-devel at rubyforge.org http://rubyforge.org/mailman/listinfo/win32utils-devel This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. From noreply at rubyforge.org Mon Aug 21 09:30:21 2006 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Mon, 21 Aug 2006 09:30:21 -0400 (EDT) Subject: [Win32utils-devel] [ win32utils-Bugs-5479 ] Incorrect SetLastError declarations Message-ID: <20060821133021.E05035241507@rubyforge.org> Bugs item #5479, was opened at 2006-08-21 04:43 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5479&group_id=85 Category: None Group: None >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: Nobody (None) >Assigned to: Daniel Berger (djberg96) Summary: Incorrect SetLastError declarations Initial Comment: windows-pr-0.5.3 lib\windows\error.rb SetLastError = Win32API.new('kernel32', 'GetLastError', 'L', 'V') SetLastErrorEx = Win32API.new('kernel32', 'GetLastError', 'LL', 'V') Should import SetLastError instead of GetLastError. ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2006-08-21 06:30 Message: Thanks. Fixed in CVS and will be released as part of 0.5.4. - Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5479&group_id=85 From noreply at rubyforge.org Thu Aug 24 00:27:45 2006 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 24 Aug 2006 00:27:45 -0400 (EDT) Subject: [Win32utils-devel] [ win32utils-Bugs-5503 ] Process::create() checks return value of CreateProcess against 0, should be false Message-ID: <20060824042745.B510C5240A91@rubyforge.org> Bugs item #5503, was opened at 2006-08-23 21:27 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5503&group_id=85 Category: win32-process Group: Code Status: Open Resolution: None Priority: 3 Submitted By: David Haney (darius42) Assigned to: Nobody (None) Summary: Process::create() checks return value of CreateProcess against 0, should be false Initial Comment: In Process::create(), the return value of CreateProcess() is compared against 0 to determine if the CreateProcess call succeeds. It appears that instead of 0, CreateProcess() will return false on a failure, and this comparison will fail (no exception). Instead a ProcessInfo with all 0 values will be returned. If the code is changed to compare against false, an exception is thrown on failure. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5503&group_id=85 From noreply at rubyforge.org Thu Aug 24 23:14:09 2006 From: noreply at rubyforge.org (noreply at rubyforge.org) Date: Thu, 24 Aug 2006 23:14:09 -0400 (EDT) Subject: [Win32utils-devel] [ win32utils-Bugs-5503 ] Process::create() checks return value of CreateProcess against 0, should be false Message-ID: <20060825031409.682EAA970027@rubyforge.org> Bugs item #5503, was opened at 2006-08-23 21:27 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5503&group_id=85 Category: win32-process Group: Code >Status: Closed >Resolution: Accepted Priority: 3 Submitted By: David Haney (darius42) >Assigned to: Daniel Berger (djberg96) Summary: Process::create() checks return value of CreateProcess against 0, should be false Initial Comment: In Process::create(), the return value of CreateProcess() is compared against 0 to determine if the CreateProcess call succeeds. It appears that instead of 0, CreateProcess() will return false on a failure, and this comparison will fail (no exception). Instead a ProcessInfo with all 0 values will be returned. If the code is changed to compare against false, an exception is thrown on failure. ---------------------------------------------------------------------- >Comment By: Daniel Berger (djberg96) Date: 2006-08-24 20:14 Message: Good catch! I've fixed it in CVS and I'll have a new release out shortly. Thanks, Dan ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=5503&group_id=85