Issue 10685 - Instant crash when trying to read a protected file from smbfs
Summary: Instant crash when trying to read a protected file from smbfs
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Linux, all
: P1 (highest) Trivial (vote)
Target Milestone: OOo 1.1 RC
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-01-15 11:24 UTC by Unknown
Modified: 2003-07-23 11:43 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Stack dump with Debian ooo1.0.2-2 on Debian x86 3.0 (5.15 KB, text/plain)
2003-05-15 16:57 UTC, dankegel 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-01-15 11:24:36 UTC 
OpenOffice 1.0.1 crashes instantly, if you try to read a file windows server, 
mounted as smbfs with user permissions, and on the windows server the user has
no permissions to that file. smbfs (at least my version) can't show if you really
have permissions to read the file, and when opening, you can get even if 
the filesystem permissions show that you should have permissions.

When trying to open the files with 'file foo.file', I get following error:
file.foo:     file: read failed (Permission denied).

Of course smbfs should be able to show correct permissions, but OpenOffice 
shouldn't crash either ;)
Comment 1 ooo 2003-01-15 12:10:40 UTC 
Hile, what makes you think that this is an API issue?  I am getting so
many bugs here in issue zilla because API was choosen as the project
where the bug belongs to, that I need to figure out, why people do
select API as the project which is responsible for the bug.  I would
appreciate an answer to this.  Thanks.

My guess is, the bug is either in the framework or in the system
file-io.  Lets try the framework team first.
Comment 2 dankegel 2003-05-15 16:57:12 UTC 
Created attachment 6213 [details]
Stack dump with Debian ooo1.0.2-2 on Debian x86 3.0
Comment 3 dankegel 2003-05-15 17:05:38 UTC 
Reproduced on OpenOffice1.0.2 (debian's package openoffice.org-1.0.2-2).
Sadly, I can't test with ooo1.1beta, which always exits
with an X i/o error on my Debian systems.

FWIW, here's the top of the stack:
#0  0x40b59dc7 in memcpy () from /lib/libc.so.6
#1  0x4054e430 in rtl_copyMemory ()
#2  0x403f973f in uno_type_sequence_assign ()
#3  0x403f82b5 in uno_type_sequence_construct ()
#4  0x41c2e6be in fileaccess::XStream_impl::readBytes
...

I can repeat under valgrind if desired.

- Dan
Comment 4 thorsten.martens 2003-05-19 09:57:20 UTC 
Trying to reproduce this problem with staroffice6.1 beta2 !
Comment 5 thorsten.martens 2003-05-19 10:52:07 UTC 
Not reproducible when using staroffice6.1 beta 2 on Mandrake Linux.
Comment 6 thorsten.martens 2003-05-19 10:59:35 UTC 
TM->MBA: HRO has taken a look into the attached stack and mentions,
that you might have an idea about what´s causing the problem. So
please have a look, thanks !
Comment 7 Mathias_Bauer 2003-05-22 10:55:00 UTC 
We have a known issue in the file ucp that might explain the observed
crash. We will try to clarify this.
Comment 8 andreas.bille 2003-05-23 14:30:19 UTC 
Changed target to RC. 
 
ABI: Was an uninitialzed variable used to realloc a buffer in case of error 
return value of sal.
Comment 9 andreas.bille 2003-05-23 14:33:21 UTC 
Changed target to RC. 
 
ABI: Was an uninitialzed variable used to realloc a buffer in case of error 
return value of sal.
Comment 10 andreas.bille 2003-05-27 12:05:25 UTC 
ABI: is in fwk04, instset available.
Comment 11 thorsten.martens 2003-05-27 12:23:50 UTC 
I´ll check this one
Comment 12 thorsten.martens 2003-05-28 09:21:22 UTC 
ABI was able to reproduce the crash and has verified the fix for this
problem. So this one is set to fixed/verified.
Comment 13 thorsten.martens 2003-05-28 09:21:43 UTC 
.
Comment 14 thorsten.martens 2003-07-23 11:43:41 UTC 
.