Closed Bug 52338 Opened 25 years ago Closed 25 years ago

Segfault using an authenticating proxy (squid)

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Platform:
x86
Linux
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 52257

People

(Reporter: cmb, Assigned: gagan)

Details

From Bugzilla Helper: User-Agent: Mozilla/4.72 [en] (X11; U; Linux 2.2.14 i686) BuildID: 2000091208 If a request is made for a URL not in the "no proxy" list, and an authenticating proxy (eg Squid) is being used, the browser segfaults when I click OK on the username/password prompt window. Reproducible: Always Steps to Reproduce: 1. Set the proxy to one that requires a username and password 2. Go to a URL not in the "no proxy" list 3. Type in a username/password, correct or otherwise, and press OK Actual Results: The console said "Document loaded successfully", and the program terminated. gdb said it was a SIGSEGV (segmentation fault), see additional info. Expected Results: Loaded the page and not segfaulted. I was not able to do mozilla-debug, gdb froze after two "new thread" messages (and repeatedly said no debugging symbols found). I _was_ able to attach gdb to a running mozilla (with the username/password dialog open), results follow: [...] Attaching to Pid 17505 0x402ecf50 in ?? () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x4079e2af in ?? () (gdb) bt #0 0x4079e2af in ?? () #1 0x4079ee3b in ?? () #2 0x4079e93e in ?? () #3 0x4079e3c8 in ?? () #4 0x407a3a34 in ?? () #5 0x407a266d in ?? () #6 0x40761ba4 in ?? () #7 0x40761450 in ?? () #8 0x400bed73 in ?? () #9 0x400bec93 in ?? () #10 0x400bf9ed in ?? () #11 0x40bbe08f in ?? () #12 0x40bbde4d in ?? () #13 0x4066faca in ?? () #14 0x40671186 in ?? () #15 0x40671751 in ?? () #16 0x406718f1 in ?? () #17 0x405a4977 in ?? () #18 0x40bbe57c in ?? () #19 0x4131718a in ?? () #20 0x804d987 in ?? () #21 0x804dde6 in ?? () --Type <return> to continue, or q <return> to quit--- #22 0x402599cb in ?? () (gdb) c Continuing. Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) quit
This has been reported a lot the past days - marking dup of the first i found, bug 52257 "Crash logging in via basic auth" *** This bug has been marked as a duplicate of 52257 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
verif. Dup
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.