| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9
Comments:
<0> should step into
<1> i would need libc debug info
<2> why
<3> hank_hill: Sure, if you're trying to debug a library.
<1> #0 0x00633cf2 in strcmp () from /lib/libc.so.6
<1> my program is hanging there
<1> i dont see the inputs
<2> don't p*** bogus pointers to it, that's why
<1> and that's invoked by glib
<2> just print 2 strings before the call
<1> i dont have the strings
<1> its called by glib
<2> do you see, called by what function ?
<1> and everything i p*** to glib makes sense
<2> try 'where' command
<1> by g_key_file_get_groups
<2> so, which function do *you* call ?
<1> g_key_file_load_from_file
<2> that's not libc function
<1> i know
<1> it's a glib
<1> i gave it all the right parameters
<2> don't lie to the court
<1> all the pointers given to the function have been allocated just before the call
<1> or all the datastructures pointed to by the pointers which were p***ed to the function were allocated
<2> that's not what you were telling the investigation, hand_hull
<1> yeah ok
<2> try valgrind
<1> interesting program
<2> oh it's good
<1> ==4936== Syscall param write(buf) points to uninitialised byte(s)
<1> i get that from X windows
<1> doesnt crash on that though
<2> uninitialized is negligible
<2> not a serious problem
<4> so quiet
<4> is everyone working?
<4> :D
<5> Yeah right. ;)
<4> :D
<4> i am productive today
<4> really!
<4> i often can't code for more than 20 minutes at work without being interrupted by something
<4> it's been 2 hours now!
<4> of course now i'm on irc
<5> That's too bad. It takes 20 minutes before you're fully concentrated.
<4> anyone here played with libotr before?
<4> it has issues
<4> context.h:typedef struct context {
<4> context.h:typedef struct fingerprint {
<4> that naming convention seems wrong for a library header
<5> Why?
<4> because the program i was implenting OTR in had naming conflicts
<5> It's not pretty, but people do the strangest things.
<4> i got around it by seperating them with wrappers
<4> but it was a pain
<6> "context" for a typedef? Tsk
<0> Hi, I come here with unusual error
<0> when I gdb
<0> I'm getting
<4> segafult?
<4> err
<0> (gdb) break 63
<0> No line 63 in file "server.c".
<4> without typo
<4> is there a line 63 in server.c?
<4> :P
<0> and I have over 100 lines in file
<7> -ggdb
<0> strtok there is
<0> Samy doesn't work
<0> I compile with
<0> -O0 -g
<0> or
<0> -O0 -ggdb
<8> ...
<0> toraton what?
<7> Break at the symbol
<0> ...?
<0> what?
<0> hey, let me show you what I have
<0> http://rafb.net/paste/results/AYxoZ163.html
<2> try b 60
<0> (gdb) b 60
<0> No line 60 in file "server.c".
<0> I can break at line 1, 15 and maybe others
<9> if(select(cli_sockfd,&cli_socketd,NULL,NULL,NULL)<0)
<9> perror("select");exit(1);
<9> does taht not look right to anyone else?
<9> and btw, condensing code into fewer lines doesn't make it run any faster
<2> if your gdb says 'I can break at line 1, 15 and maybe others'
<2> then ...
<2> he's got too much intellect
<2> i'd fear it
<0> hehe
<0> no DynaMish I figured that out
<2> i wodn't my gdb to say such things at me
<10> haha
<5> buf[0][i++]='\0',strncpy(&buf[1][1],buf[0],strlen(buf[0])+1),targetp=strstr(&buf[1][1],"GET");
<2> jis is hutspah
<5> Does that even make sense?
<9> heh, didn't think ppl still used bzero()
<0> _reppir bzero?
<9> hund: what are you trying to do?
<2> rumors of death of bzero() were unjustified
<9> ahh my mistake DynaMish :)
<0> Where do I use bzero ?
<9> line 33
<0> yes, I use bcopy but not bzero
<9> but that line with the strcpy() makes my brain hurt
<9> bzero(&(my_addr.sin_zero), 8); /* zero the rest of the struct */
<9>
<9> sorry for the pasting :\
<0> _reppir ok I see it
<6> bcopy and bzero are deprecated, aren't they?
<0> copied it from some web page
<9> they are in C++, wasn't sure about C
<11> memset, and memcpy took over i think
<9> they are probably just macros for memset/memcpy anyway
<6> Yes, and memmove
<5> I_v0: It's the rightmost operand to the comma operator that is returned.
<2> Maloeran: if 'deprecated' means 'here, forever', then yes
<0> ok ok, please help don't ride on me so much
<0> :(
<9> I recommend first cleaning things up a bit
<9> it's difficult to see what all is going on
<0> I'm sure I don't know 1% of what you know, but still would want to learn
<9> for example, the child code could easily be moved into a separate function
<9> how did you come upon 1507 for QUERYSIZE?
<5> I_v0: Well, the code is unreadable.
<2> And even gdb thiks so
<0> _reppir I listened for packets seens somwhere 1507, tohugh I know tcp/ip packets should have 1500
<6> Ahah
<0> yhm 1506
<0> :)
<9> don't worry about the packets, that is hardware level stuff
<9> this is at the application layer, I recommend you focus on the data you want at that layer
<6> The hardware and kernel care about this stuff for you
<9> for example, the max size of an http GET reply
<0> _reppir yeah, but I though it would be fine to save as much as comes
<2> I_v0: why do you need select at all, if all you need is recv() frmo 1 socket w/o timeout ?
<9> absolutely, so why not make it 10000 ? :)
<2> Use of select here is pretty purposeless
<0> DynaMish I need to select becouse otherwise when I nc 127.0.0.1:12345 it drops me after 1 letter
<6> There is no maximum size for http queries, you need to read content-length
<0> DynaMish also in future I plan to give some timeout
<0> Maloeran it's what I plan to do, as you see in bottom
<9> http://rafb.net/paste/results/ANgMvD51.html
<2> all your indentation is totally scrwed
Return to
#c
or
Go to some related
logs:
#cph
#beginner
eksusa765pci jumper
#gentoo
#linux-noob
#cisco
ubuntu pymssql
#worldcup
I need my space bullshit
#stocks
|
|