Eno.
txs for the tip, I've run that, although there's not much I can use
there. I post it here the ending lines of the log "just in case"
write(1, "\33[32;1mok 46\33[0m - getNextNumber"..., 70) = 70
_llseek(1, 18446744073709551615, 0xbf905330, SEEK_SET) = -1 ESPIPE
(Illegal seek)
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon
echo ...}) = 0
write(1, "\33[37;42;1m Looks like everything"..., 86) =
86 <----- here it should end the test.
poll([{fd=3, events=POLLIN|POLLPRI}], 1, 0) = 0
write(3, "\1\0\0\0\1", 5) = 5
shutdown(3, 2 /* send and receive */) = 0
close(3) = 0
socket(PF_FILE, SOCK_DGRAM, 0) = 3
connect(3, {sa_family=AF_FILE, path="/dev/log"}, 110) = 0
send(3, "<9>suhosin[17577]: ALERT - possi"..., 143, 0) = 143
close(3) = 0
write(2, "ALERT - possible memory corrupti"..., 124) = 124
exit_group(1) = ?
this log correspond to the following error message (always after the
"looks like everything went fine" message)
ALERT - possible memory corruption detected - unknown Hashtable
destructor (attacker 'REMOTE_ADDR not set', file 'unknown')
also, I get these other error messages (again, randomly)
- zend_mm_heap corrupted
- ALERT - canary mismatch on efree() - heap overflow detected
(attacker 'REMOTE_ADDR not set', file 'unknown')
txs again.
On Sep 15, 11:08 am, Eno <symb...@gmail.com> wrote:
> On Tue, 15 Sep 2009, JoeZ wrote:
> > JoeZ# ./symfony test:unit model/Invoice
> > 1..46
> > # Totals checks
> > ok 1 - we have created an Invoice which contains 3 items
> > ok 2 - getBase() == 224.98
> > ...
> > ....
> > ok 44 - getNextNumber of ASET- invoices will be 10
> > ok 45 - getNextNumber of BSET- invoices will be 6
> > ok 46 - getNextNumber of CSET- invoices will be 7
> > Looks like everything went
> > fine.
> > Segmentation fault
>
> > my PHP:
> > PHP 5.2.8-1hardy~ppa1 with Suhosin-Patch 0.9.6.3 (cli) (built: Jan 6
> > 2009 13:28:48)
> > Copyright (c) 1997-2008 The PHP Group
> > Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
>
> > my System Ubunty Hardy Heron 8.04
>
> > let me insist: the "segmentation fault" does not happen always, how am
> > I supposed to debug this???
>
> On Linux machines, you can run strace to log all system calls and see
> where the seg fault occurs.
>
> --
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
