Segfault on POST
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apache2 Web Server |
Fix Released
|
High
|
|||
apache2 (Mandriva) |
Unknown
|
Critical
|
|||
apache2 (Ubuntu) |
Fix Released
|
High
|
Chuck Short | ||
Natty |
Fix Released
|
High
|
Chuck Short |
Bug Description
Binary package hint: apache2
It seems that problem is well known:
https:/
https:/
(gdb) bt
#0 0x00000058 in ?? ()
#1 0x0018f024 in ap_discard_
#2 0x0016f96f in default_handler (r=0x218eee38) at /build/
#3 0x0017b181 in ap_run_handler (r=0x218eee38) at /build/
#4 0x0017b589 in ap_invoke_handler (r=0x218eee38) at /build/
#5 0x0018ce58 in ap_process_request (r=0x218eee38) at /build/
#6 0x00189ba8 in ap_process_
#7 0x00182761 in ap_run_
#8 0x00193343 in process_socket (thd=0x218a54d0, dummy=0x218dbbe0) at /build/
#9 worker_thread (thd=0x218a54d0, dummy=0x218dbbe0) at /build/
#10 0x00ae8a35 in ?? () from /usr/lib/
#11 0x00e3fe79 in start_thread (arg=0xb0748b70) at pthread_
#12 0x006bd6ae in clone () at ../sysdeps/
(gdb) ^CQuit
(gdb)
Changed in apache2 (Ubuntu): | |
status: | New → Confirmed |
Changed in apache2 (Ubuntu): | |
assignee: | nobody → shankao (shankao) |
status: | Confirmed → In Progress |
tags: | added: natty |
Changed in apache2 (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in apache2 (Ubuntu Natty): | |
assignee: | shankao (shankao) → Chuck Short (zulcss) |
Changed in apache2 (Ubuntu Natty): | |
milestone: | none → natty-alpha-2 |
Changed in apache2: | |
importance: | Unknown → High |
status: | Unknown → Confirmed |
Changed in apache2 (Mandriva): | |
importance: | Unknown → Critical |
Changed in apache2: | |
status: | Confirmed → Fix Released |
In upstreams bug comments, is suggested that the bug can be a regression in gcc 4.5 optimizations [0]
This produces lots of problems with apache in natty (gcc 4.5). Should we mark it as medium importance?
[0] http:// gcc.gnu. org/bugzilla/ show_bug. cgi?id= 46488