| |
| |
| |
|
Page: 1 2
Comments:
<0> hello
<1> hey
<0> hoi
<1> how are you?
<0> so and so
<0> trying to get serial isa card working
<0> ( = dumbo work)
<0> you>?
<1> just ircing, nothing useful out of me today ;)
<0> righto
<0> brainphart: char aa[ 3 ][ 4 ] is array of 3 arrays of 4 chars, right?
<0> c'mon guys :)
<0> well, you ****.
<1> yes michai
<0> right
<2> r8
<3> reight?
<2> yea, in pronounciation
<1> essato!
<0> tutti[3][4]
<0> bugger
<4> hi
<4> what file must i run to open process manager
<4> ?
<4> in win 2000?
<0> I am guessing taskmgr.exe
<0> it's not a C question is it?
<4> no
<4> :)
<0> laters
<5> hello
<5> somebody know what rules i must respect for create efficent functions ?
<5> efficent and speed
<5> or some program that analise a source that contain a function definition
<6> try valgrind
<7> .
<2> what does mean confliting types
<2> ?
<2> I have proper types declared
<7> http://rafb.net/paste/results/M6X1pJ78.html
<7> is possible change this program for be more speed ?
<8> I_v0: your compiler does not agree.
<8> K-engineer: don't call realloc so often.
<6> K-engineer: http://www.pipapo.org/cgi-bin/archzoom.cgi/chth@gmx.net--2004/callsystem--cehteh--0.1--patch-16/callsystem.c near the end is a 'reserve_string' funktion try it that way
<9> there is someonw?
<9> i have a bug
<8> probably not.
<9> that trigger only
<9> when i start my program from a shell script
<9> it is a client-like program
<9> if i start it 3 times with &
<9> then it trigger the bug
<9> but if i do the same from a normal shell
<9> it doesn't
<9> any idea?
<9> :\
<9> no.. even simpler
<9> from a shell script it doesn't work
<9> from console yes
<9> O_o
<8> how can you tell that it has a bug?
<3> guess-the-bug again, now with even less info.
<9> Auris, i'm working from 20 hours :)
<8> i.e., what happens, and what did you expect?
<9> just to finish that stupid stuff
<9> it is somewhat related to signals
<9> well. the question is
<9> myprog &
<9> myprog
<9> what is the difference? :)
<9> shell doesn't wait for termination
<8> not much.
<8> if the first program tries to read or write the tty it will likely be stopped to wait to be made the foregound process.
<9> stopped by who?
<9> blocked in the call?
<8> the kernel.
<8> but, rather than us guessing, why don't you tell us how you know there is a bug.
<9> the program should quit
<9> but it doesn't quit if started from a shell script with &
<9> if i remove the & it does work
<3> how do you know it does not quit?
<8> you probably just don't notice it quitting.
<9> if i take the entire command with the & and run it in a shell.. it does work
<9> but & + shell script => don't work
<8> ohh, don't work.
<9> :)
<8> that is very descriptive.
<9> i know :\
<8> so be descriptive you dork.
<9> there is a thread
<9> blocked in sigwaitinf()
<9> waiting for another thread to send him a SIGINT
<9> any idea?
<9> signals.. shells..
<3> nope.
<8> threads and signals are not very easy to get right.
<9> twkm, i had been very carefull..
<9> my problem here is that i can't simulate this bug with debugging tools like gdb or strace :\
<8> do you block the signal in all threads except th one that you want to receive it?
<9> yes
<9> i send this signal with pthread_kill to
<9> to the specified thread
<9> maybe it is this foreground/background story
<8> does your program attempt any terminal i/o?
<9> no..
<9> aaaaaaah
<9> i have found :>
<9> no
<8> sounds like it is time for you to create a test case.
<9> :>
<3> calls for printf-debugging.
<8> in a threaded program that can be tricky.
<9> puts("ok1");
<9> if (pthread_kill(client->main,SIGINT))
<9> abort();
<9> puts("ok2");
<9> both ok1 and ok2 are called.. but the other thread will block forever on sigwaitinfo
<9> ok1 and ok2 are written..
<9> signals should queu right?
<9> if the signal come before the sigwaitinfo..
<9> and it is blocked
<9> then it should be queued.. correct?
<9> mm
<9> i replaced pthread_kill with kill
<9> but no.. the problem remain
<9> :D
<9> with a sched_yield
<9> just before the sigwaitinfo
<9> the problem disappear
<8> sounds like you have a poor threading ***umption.
<9> these sched_yield are here just to debug :)
<9> i don't want to rely on them obviusly
<9> twkm, isn't that strange?
<9> pthread_kill after sigwaitinfo isn't good? :o
<9> :)
<9> using SIGUSR1 instead of SIGINT is ok
<9> probably it is bash that does somethings like wait().. and it somewhat intercept the SIGINT..
<3> mmh.
<9> Auris, if you are idle i can repeat the question about the pthread_cancel
<9> and valgrind :)
<9> it is yet an open question.. at least for me :)
<10> moin
<11> re
<12> good morning...
<13> hm. I have a piece of code like: char *a; a=malloc(10); a[0]='\0'; strcat (a,somestring); Valgrind is yelling "Conditional jump or move depends on uninitialised value" in this strcat()... any ideas?
<0> hoi
<12> bgd: goto/fork/vfork before the declaration of the variable?
<13> char *a; a=malloc(); a[0]='\0'; for (i=0;...) { strcat(a,other_string[i]); ....}
<13> denk: between the declaration of a and the a=malloc() are only some while loops and if statements in which I'm playing with a. No fork, no vfork, no goto
<12> and longjump?
Return to
#c
or
Go to some related
logs:
#worldchat
balatkar video
#worldchat
#worldchat
#worldchat
#worldchat
miss teeqy
#london
#worldchat
bad bool value in config file for: ssl_enable
|
|