Groups | Search | Server Info | Login | Register
Groups > comp.lang.asm.x86 > #8826
| From | Borax Man <rotflol2@nospicedham.hotmail.com> |
|---|---|
| Newsgroups | comp.lang.asm.x86 |
| Subject | Re: Debugger problems |
| Date | 2023-12-04 12:01 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <ukkf3m$3dbv4$2@dont-email.me> (permalink) |
| References | (2 earlier) <ukesnb$2a8g9$1@dont-email.me> <kt18crF1b8hU1@mid.individual.net> <ukhhrg$2q0aj$3@dont-email.me> <kt3phrFlp8jU1@mid.individual.net> <20231204181048.43ae1234@hotmail.com> |
On 2023-12-04, Borax Man <rotflol2@nospicedham.hotmail.com> wrote: > On 3 Dec 2023 16:43:39 GMT > Tavis Ormandy <taviso@nospicedham.gmail.com> wrote: > >> On 2023-12-03, Borax Man wrote: >> > On 2023-12-02, Tavis Ormandy <taviso@nospicedham.gmail.com> wrote: >> >> On 2023-12-02, Borax Man wrote: >> >>> NASM can generate debugging information which I believe will generate >> >>> line info. Pass '-F dwarf' option to nasm if under Linux, and you should see each >> >>> line of source in the debugger. >> >> >> >> You're thinking of line markers I think (like %line 123), but I think >> >> Martijn wants the assembler to do that automatically so that b >> >> foo.asm:123 works, like it does in gas. >> >> >> >> As far as I know nasm won't do that? >> >> >> > >> > I did a test using nasm with the '-F dwarf' and '-g' parameters, and I >> > was able to add breakpoints in GDB specifying the line using the >> > syntax you mentioned. >> >> Weird.... and this is for elf64? >> >> Perhaps you have a newer version than me, good to know it will arrive eventually! >> >> Tavis. > > I tested this on Debian 12... 32 bit (my laptop is old). > > Just to clarify, NASM version 2.16.01.
Back to comp.lang.asm.x86 | Previous | Next — Previous in thread | Next in thread | Find similar
Debugger problems Martijn Bos <martijnm.bos@gmail.com> - 2023-11-30 01:00 -0800
Re: Debugger problems Tavis Ormandy <taviso@nospicedham.gmail.com> - 2023-12-02 00:28 +0000
Re: Debugger problems Borax Man <rotflol2@nospicedham.hotmail.com> - 2023-12-02 09:17 +0000
Re: Debugger problems Martijn Bos <martijnm.bos@nospicedham.gmail.com> - 2023-12-02 03:04 -0800
Re: Debugger problems Tavis Ormandy <taviso@nospicedham.gmail.com> - 2023-12-02 17:38 +0000
Re: Debugger problems Borax Man <rotflol2@nospicedham.hotmail.com> - 2023-12-03 09:30 +0000
Re: Debugger problems Tavis Ormandy <taviso@nospicedham.gmail.com> - 2023-12-03 16:43 +0000
Re: Debugger problems Borax Man <rotflol2@nospicedham.hotmail.com> - 2023-12-04 18:10 +1100
Re: Debugger problems Borax Man <rotflol2@nospicedham.hotmail.com> - 2023-12-04 12:01 +0000
Re: Debugger problems Martijn Bos <martijnm.bos@nospicedham.gmail.com> - 2023-12-06 03:55 -0800
Re: Debugger problems Martijn Bos <martijnm.bos@nospicedham.gmail.com> - 2023-12-02 02:12 -0800
csiph-web