fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
hpt has joined #systemtap
orivej has quit [Ping timeout: 252 seconds]
orivej has joined #systemtap
orivej has quit [Ping timeout: 265 seconds]
higgins has quit [Quit: Leaving]
higgins has joined #systemtap
orivej has joined #systemtap
hpt has quit [Ping timeout: 268 seconds]
hpt has joined #systemtap
mjw has joined #systemtap
khaled has quit [Quit: Konversation terminated!]
khaled has joined #systemtap
hpt has quit [Ping timeout: 240 seconds]
khaled has quit [Remote host closed the connection]
khaled has joined #systemtap
wcohen has quit [Ping timeout: 265 seconds]
tromey has joined #systemtap
khaled has quit [Quit: Konversation terminated!]
khaled has joined #systemtap
cdleonard has quit [Read error: Connection reset by peer]
cdleonard1 has joined #systemtap
cdleonard1 has left #systemtap [#systemtap]
orivej has quit [Ping timeout: 240 seconds]
amerey has joined #systemtap
<lijunlong>
fech, which solution do you prefere? mutiple entries with base addr or one entry with start and end but have hole in it?
<fche>
lijunlong, can you think of some bad consequence of the hole? might something be mapped in there later, or some symbol resolve into it?
<fche>
if so, then let's have separate entries
<fche>
but not same base addr right?
<lijunlong>
all the symbols(functions/variables) should have the same base addr although in different map segments.
<lijunlong>
stap check the module first, so if something be mapped in there, still works well.
<lijunlong>
sorry, I am wrong. if something mapped into the hole, may get wrong symbol.
<lijunlong>
so the safer way is keep multiple entries and got base address from the first segment of the module.