[Mono-bugs] [Bug 478652] UnixDirectoryInfo.Delete() won't throw an exception for non-existent directory
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Mon Feb 23 09:33:00 EST 2009
https://bugzilla.novell.com/show_bug.cgi?id=478652
User jpryor at novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=478652#c1
Jonathan Pryor <jpryor at novell.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |jpryor at novell.com
Info Provider| |flz at xbsd.org
--- Comment #1 from Jonathan Pryor <jpryor at novell.com> 2009-02-23 07:32:59 MST ---
I can't reproduce:
mono n478652.exe
Unhandled Exception: System.IO.FileNotFoundException: No such file or directory
---> Mono.Unix.UnixIOException: No such file or directory [ENOENT].
at Mono.Unix.UnixMarshal.ThrowExceptionForLastError () [0x00000]
at Mono.Unix.UnixDirectoryInfo.GetEntries () [0x00000]
at Mono.Unix.UnixDirectoryInfo.GetFileSystemEntries () [0x00000]
at Mono.Unix.UnixDirectoryInfo.Delete (Boolean recursive) [0x00000]
at TestDelete.Main () [0x00000]
This is for both Mono 2.0 and mono 2.5 (trunk r127307).
>From the look of the stack trace, it's crashing while trying to call into
MonoPosixHelper.
The questions are:
1. What distro and Mono version is this under?
2. What exception (if any) is being thrown? If it's a DllNotFoundException,
then MonoPosixHelper isn't being found (odd). If it's just dying for no
particular reason, this could be a bug within
MonoPosixHelper:Mono_Posix_Syscall_strerror_r() (in mono/support/errno.c).
If possible, could you build MonoPosixHelper with debug symbols, run mono
within gdb, and get a backtrace when it crashes (assuming it's dying from a
SIGSEGV):
$ gdb `which mono`
(gdb) r your-app.exe
.. program crashes
(gdb) bt
Note that this will require debug symbols for MonoPosixHelper to be useful.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the mono-bugs
mailing list