Scott,
I've been using this Aolserver 3.0 + PHP 4.0.6 for over a year with no
problem -- this is new (mis)behavior. In what I'm trying to setup now, the
PHP version is the same, but I'm trying to use new versions of Aolserver
(3.4.2) and RedHat (7.2, old server has 6.2). I cannot think of any
I hate to say it, but drop back to 3.0 and test on RH 7.2. If it breaks,
then there's something different in the combo between AOLserver and RedHat
7.2.
If it works, then upgrade to AOLserver 3.1 and test, then 3.2 and test etc.
until you get to 3.4.2, also on RedHat 7.2. Let's find out which
At 11:24 AM 11/27/2001 -0500, Scott Goodwin wrote:
I hate to say it, but drop back to 3.0 and test on RH 7.2. If it breaks,
then there's something different in the combo between AOLserver and RedHat
7.2.
Actually, I tried that and ran into the same problem.
Sean Redmond
Brooklyn Museum of Art
Ok, then it sounds like an interaction problem between AOLserver and RedHat
7.2 (or more likely the PHP module and 7.2).
Can you post the backtrace?
/s.
At 11:24 AM 11/27/2001 -0500, Scott Goodwin wrote:
I hate to say it, but drop back to 3.0 and test on RH 7.2. If it breaks,
then there's
On 2001.11.27, Scott Goodwin [EMAIL PROTECTED] wrote:
Frankly, I'm surprised that a bad path would cause a segfault, which leads
me to believe that some var or pointer isn't being initialized before use.
My WAG would be that this is some keep people from busting out of
a chroot jail code
At 12:22 PM 11/27/2001 -0500, you wrote:
On 2001.11.27, Scott Goodwin [EMAIL PROTECTED] wrote:
Frankly, I'm surprised that a bad path would cause a segfault, which leads
me to believe that some var or pointer isn't being initialized before use.
My WAG would be that this is some keep people
On Tuesday 27 November 2001 12:22 pm, Dossy wrote:
On 2001.11.27, Scott Goodwin [EMAIL PROTECTED] wrote:
Frankly, I'm surprised that a bad path would cause a segfault, which
leads me to believe that some var or pointer isn't being initialized
before use.
My WAG would be that this is some
On 2001.11.27, Sean Redmond [EMAIL PROTECTED] wrote:
0x400afdd3 in canonicalize (
name=0x8396940
/usr/local/aolserver-3.0/servers/webmail/pages/squirrelmail-1.2.0-rc2/src/../src/load_prefs.php,
resolved=0x403bc12c )
at canonicalize.c:88
88 canonicalize.c: No such file or
At 01:22 PM 11/27/2001 -0500, you wrote:
Could you add the directory containing the PHP source to your
gdb init, as well, and send that backtrace? I'm guessing that's
where canonicalize.c lives, and it'd be interesting to see what
line 88 is actually doing that causes the segfault ...
I did
On 2001.11.27, Sean Redmond [EMAIL PROTECTED] wrote:
At 01:22 PM 11/27/2001 -0500, you wrote:
Could you add the directory containing the PHP source to your
gdb init, as well, and send that backtrace? I'm guessing that's
where canonicalize.c lives, and it'd be interesting to see what
line 88
(gdb) up
#1 0x40291659 in virtual_file_ex (state=0x403ac164,
path=0x833a694 ../src/load_prefs.php, verify_path=0)
at tsrm_virtual_cwd.c:299
299 if (realpath(tmp, resolved_path)) {
(gdb) list
294 ptr += state-cwd_length;
295
Okay. Could you provide the source for the entire virtual_file_ex()
function from tsrm_virtual_cwd.c file?
-- Dossy
On 2001.11.27, Sean Redmond [EMAIL PROTECTED] wrote:
(gdb) up
#1 0x40291659 in virtual_file_ex (state=0x403ac164,
path=0x833a694 ../src/load_prefs.php, verify_path=0)
My next suggestion will require learning a bit of gdb, but
I'd try setting a breakpoint on line 298, and when it stops
I'd inspect what's actually contained in *tmp.
Why they built *ptr (and thus, *tmp) the way they did
baffles me, too.
One suggestion, delete line 287 (I think) which I'm
At 03:27 PM 11/26/2001 -0500, you wrote:
Hi Sean,
have you run AOLserver under GDB yet to find out where it is segfaulting?
Here's an example of how to do that.
Thanks. It is happening when in the PHP statement
include ../src/load_prefs.php;
The relative path is expanded to
human than most.
Scott S. Goodwin
u: http://scottg.net
e: [EMAIL PROTECTED]
p: 850.897.6830
aim: scottgnet
- Original Message -
From: Sean Redmond [EMAIL PROTECTED]
To: AOLserver Discussion [EMAIL PROTECTED]
Sent: Monday, November 26, 2001 4:06 PM
Subject: Re: [AOLSERVER] Again, Segfault
Hi Sean,
have you run AOLserver under GDB yet to find out where it is segfaulting?
Here's an example of how to do that.
Put this into a file called gdbinit, substituting the things in parens with
something appropriate and adjusting pathnames:
=== BEGIN : CUT ==
directory
16 matches
Mail list logo
