public inbox for trinity@vger.kernel.org
 help / color / mirror / Atom feed
* stack smash detected bug
@ 2013-10-04  1:53 Ildar Muslukhov
  2013-10-04 15:29 ` Dave Jones
  0 siblings, 1 reply; 6+ messages in thread
From: Ildar Muslukhov @ 2013-10-04  1:53 UTC (permalink / raw)
  To: Dave Jones, trinity

Hi,

I've been looking through the strange behavior today, where I am
getting lots of "stack smashing detected" and found that the most
probable place is the mkcall function. Here is the call stack:
[0x440545] (stack check related calls)
[0x44050e] (stack check related calls)
[0x408db4]<-stack canary check
[0x412709]<-call mkcall
[0x402228]
[0x405586]
[0x40185a]
[0x412b44]
[0x401db1]<-main()

After looking into the code in mkcall:
>long mkcall(int childno)
>{
>        unsigned long olda1, olda2, olda3, olda4, olda5, olda6;
>        unsigned int call = shm->syscallno[childno];
>        unsigned long ret = 0;
>        int errno_saved;
>        char string[512], *sptr;
...
I suspect that string[512] is the issue. The simple tests confirms
that assumption (I've just commented out the block of color_arg
function calls that fill the buffer with parameter values).

Will provide a patch for that tomorrow.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-10-04 17:40 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-04  1:53 stack smash detected bug Ildar Muslukhov
2013-10-04 15:29 ` Dave Jones
2013-10-04 17:11   ` Ildar Muslukhov
2013-10-04 17:17     ` Dave Jones
2013-10-04 17:30       ` Ildar Muslukhov
2013-10-04 17:40         ` Dave Jones

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox