WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
169154
Add support for relative pathnames to JSC config files
https://bugs.webkit.org/show_bug.cgi?id=169154
Summary
Add support for relative pathnames to JSC config files
Michael Saboff
Reported
2017-03-03 16:11:02 PST
There are two relative path support issues. 1) To allow for log file names relative to where the config file is located. 2) To determine the absolute path of the config file when a relative name is used. This is needed so that issue #1 can be addressed.
Attachments
Patch
(5.22 KB, patch)
2017-03-03 16:22 PST
,
Michael Saboff
saam
: review+
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Michael Saboff
Comment 1
2017-03-03 16:22:00 PST
<
rdar://problem/30844619
>
Michael Saboff
Comment 2
2017-03-03 16:22:37 PST
Created
attachment 303355
[details]
Patch
Saam Barati
Comment 3
2017-03-03 16:37:36 PST
Comment on
attachment 303355
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=303355&action=review
r=me
> Source/JavaScriptCore/runtime/ConfigFile.cpp:434 > + if (sizeof(filenameBuffer) - 1 > pathnameLength + shouldAddPathSeparator) {
Why not >=?
Michael Saboff
Comment 4
2017-03-03 16:45:27 PST
(In reply to
comment #3
)
> > Source/JavaScriptCore/runtime/ConfigFile.cpp:434 > > + if (sizeof(filenameBuffer) - 1 > pathnameLength + shouldAddPathSeparator) { > > Why not >=?
I think you're right, >= is fine. I made that change.
Michael Saboff
Comment 5
2017-03-03 17:09:50 PST
Committed
r213399
: <
http://trac.webkit.org/changeset/213399
>
Carlos Alberto Lopez Perez
Comment 6
2017-03-03 21:01:57 PST
Committed
r213416
: <
http://trac.webkit.org/changeset/213416
>
Darin Adler
Comment 7
2017-03-04 10:16:52 PST
I don’t think we need an #if around include of <unistd.h>. Do we compile on any platform that does not have a header by that name?
Michael Catanzaro
Comment 8
2017-03-04 12:58:12 PST
Surely Windows does not have unistd.h? Is that wrong?
Darin Adler
Comment 9
2017-03-05 12:11:15 PST
(In reply to
comment #8
)
> Surely Windows does not have unistd.h? Is that wrong?
I had though we had some sort of compatibility version of <unistd.h> for Windows, but looking at the rest of our code it seems that we don’t. (I see an unguarded include of that header in WebProcess.cpp, but I think that’s in code we don’t compile for Windows. I think there used to be a compatibility version of the header inside ANGLE, but not any more and we wouldn’t have wanted to rely on it anyway. Instead we include <unistd.h> in a few different places, each time with a different #if. So I guess this makes it no worse.)
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug