* gcc killed message
@ 2006-05-14 1:50 Dimitrios Tsoumakos
2006-05-14 6:12 ` Sven Eschenberg
0 siblings, 1 reply; 2+ messages in thread
From: Dimitrios Tsoumakos @ 2006-05-14 1:50 UTC (permalink / raw)
To: gcc-help
hi, can you help me with the following (probably easy) qu:
Compilation goes great but probably after i increase the size of some
tables, program doesnt even start and 'killed' appears. Is this fixable
with gcc parameters or is it OS defined?
Thank you,
D
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: gcc killed message
2006-05-14 1:50 gcc killed message Dimitrios Tsoumakos
@ 2006-05-14 6:12 ` Sven Eschenberg
0 siblings, 0 replies; 2+ messages in thread
From: Sven Eschenberg @ 2006-05-14 6:12 UTC (permalink / raw)
To: Dimitrios Tsoumakos; +Cc: gcc-help
I asume this 'killed' you are talking about is produced by a SIGKILL
your process received. The question might be though, why it should
receive a SIGKILL.
-Sven
Dimitrios Tsoumakos wrote:
> hi, can you help me with the following (probably easy) qu:
> Compilation goes great but probably after i increase the size of some
> tables, program doesnt even start and 'killed' appears. Is this
> fixable with gcc parameters or is it OS defined?
>
> Thank you,
> D
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-05-14 6:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-05-14 1:50 gcc killed message Dimitrios Tsoumakos
2006-05-14 6:12 ` Sven Eschenberg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).