[linux] [sergi...@debian.org: Toronto Bug Squashing Party in April]
A Debian Bug Squashing Party in Toronto is taking shape for the last Saturday of April - at Mozilla HQ. See info below, which was sent to Montreal/Quebec Debian User Group. Note the wiki which is being used for organizing - I'm sure details will change as the date approaches so keep checking back. bjb - Forwarded message from Sergio Durigan Junior - Date: Wed, 03 Apr 2019 01:52:51 -0400 From: Sergio Durigan Junior Subject: Toronto Bug Squashing Party in April To: debian-dug-que...@lists.debian.org Cc: Samuel Vale , Alex Volkov Salut, mes amis, I would like to invite you to the first Toronto Bug Squashing Party, to be held on Saturday, April 27th, 2019, at the Mozilla Toronto office. First things first: you can find the most up-to-date information about the event at our wiki page: https://wiki.debian.org/BSP/2019/04/ca/Toronto We are still at the early stages of planning the event, but we thought it would be a good idea to send this e-mail early for you guys and gals in Montréal. Because this is the first BSP in Toronto (ever, probably), and it's also the first BSP that Samuel, Alex and I are organizing, I decided to get in touch with anarcat and invite him to come to Toronto and give his "Packaging 101" talk. He has already given us a few advices on how to proceed, and has kindly 99%-accepted (if I understood correctly) the invitation (thanks!). I know our cities are not really close to each other, and I know that travelling for a one-day event can be tough, but we would love to see more members of the Debian Québécois movement here with us. This event will be important because, if all goes right, it will help us bootstrap a much needed Debian community here in Toronto (I still can't believe we don't have one). Anyway, now the invitation has been made! Feel free to put your names on the wiki page if you're coming, and let the discussions begin. Merci, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ - End forwarded message - To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org To get help send a blank message to linux+h...@linux-ottawa.org To visit the archives: https://lists.linux-ottawa.org
Re: [linux] readelf/objdump to dump included symbols and including source files?
On Sun, 7 Apr 2019, Stephen M. Webb wrote: > On 2019-04-07 11:55 AM, Robert P. J. Day wrote: > > > > i'm sure that, once upon a time, using either readelf or objdump, i > > found a variation with a certain collection of options that displayed > > no more than each included routine in the final ELF file and the > > source file it came from. and at the moment, i am completely > > forgetting how i did it. > > A stripped ELF file is not going to have any debug information (eg. > the source file from which a bunch of binary objects in a particular > segment was compiled). If you're creating the boot image you might > need to tweak things so the debug information doesn't get stripped > out during the build. > > The debug information is stored in DWARF tables inside of the ELF > file. Try playing with the --debug-dunmp and the --dwarf-* options > to readelf. except i'm *sure* that i did this once upon a time without tweaking the compile stage. i'll try to figure out how i did this before, unless i'm misremembering what i did. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org To get help send a blank message to linux+h...@linux-ottawa.org To visit the archives: https://lists.linux-ottawa.org
Re: [linux] readelf/objdump to dump included symbols and including source files?
On 2019-04-07 11:55 AM, Robert P. J. Day wrote: > > i'm sure that, once upon a time, using either readelf or objdump, i > found a variation with a certain collection of options that displayed > no more than each included routine in the final ELF file and the > source file it came from. and at the moment, i am completely > forgetting how i did it. A stripped ELF file is not going to have any debug information (eg. the source file from which a bunch of binary objects in a particular segment was compiled). If you're creating the boot image you might need to tweak things so the debug information doesn't get stripped out during the build. The debug information is stored in DWARF tables inside of the ELF file. Try playing with the --debug-dunmp and the --dwarf-* options to readelf. -- Stephen M. Webb To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org To get help send a blank message to linux+h...@linux-ottawa.org To visit the archives: https://lists.linux-ottawa.org
[linux] readelf/objdump to dump included symbols and including source files?
while i'm asking this in the context of an ARM-based u-boot ELF executable (for which i have all the corresponding ARM-related utilities), i suspect it would work equally well on native ELF files. in u-boot source, there are many examples of the same function being defined in multiple places in the code, and the configuration responsible for selecting one of them to be compiled and built into the final ELF image. the first technique is, of course, that the board configuration will end up including only the appropriate version of the routine. the second technique is that a common implementation might be declared with the "weak" attribute, while specific boards or architectures might override that. in any event, the final executable will, for these routines, have a single included version of that routine that came from a particular source file, and that's what i want to print out. i'm sure that, once upon a time, using either readelf or objdump, i found a variation with a certain collection of options that displayed no more than each included routine in the final ELF file and the source file it came from. and at the moment, i am completely forgetting how i did it. thoughts? surely this can't be hard, it's just escaping me right now. rday To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org To get help send a blank message to linux+h...@linux-ottawa.org To visit the archives: https://lists.linux-ottawa.org
